Log file scanner

Related content No related content found. Still need help? The Atlassian Community is here for you. Was this helpful? Yes No It wasn't accurate. It wasn't clear. It wasn't relevant. Powered by Confluence and Scroll Viewport. This command gathers and saves all exported logs to the AIPLogs. Any folders in the path must already exist.

If you specify a file name that already exists in the specified folder, the original file is overwritten. To use this parameter, you must run your PowerShell session with the Run as Administrator option. Specifies the variable that includes the credentials object to use when you need to export log files from an account other than the account you are currently signed in with. For example, you need to collect log files for the service account that runs the Azure Information Protection scanner.

In this scenario, if the scanner is installed on the same computer as you're running this cmdlet, the log files also include some information from the scanner's configuration database.

If native executable doesn't work, use the JAR instead. Paths should be separated by new line. Prepend for comment. This option may slow down scanning. System default charset is used if not specified. With --scan-log4j1 option, it also removes JMSAppender. Don't use this option unless you know what you are doing. If --backup-path is specified, this option is ignored. Spaces are not allowed here. Does not support relative paths.

Supports fragments. Send vulnerable, potentially vulnerable, and mitigated reports by default. Specify alert for vulnerable and potentially vulnerable reports. Specify info for vulnerable, potentially vulnerable, and mitigated reports.

Specify debug for vulnerable, potentially vulnerable, mitigated, and error reports. Facility value must be in the range of 0 to 23 inclusive. Implies --report-csv. If log file exists, log will be appended.