Manage Cloud server location for storing automation logs - For Cloud deployments, administrators can use the Automation Logs settings to choose between Control Room location or SIEM to store the custom logs. This enables administrators to analyze these log files if any automation encounters an error after deployment and helps them identify the root cause for that error.

For Cloud deployments, administrators can use the Automation Logs settings to choose between Control Room location or SIEM to store the custom logs. This enables administrators to analyze these log files if any automation encounters an error after deployment and helps them identify the root cause for that error.

Procedure

Log in to the Control Room.
Navigate to Administration > Settings.
Click the Automation Logs drop- down menu.
Option to change the default location for storing the automation logs is displayed.
Click Edit.
Use the Server Location filed to select one of the following options:
- Control Room - Is the default server location where the automation logs are stored. For more information, see Control Room log files.
  (Optional) Click the Log level threshold drop-down menu to select one of the following options for displaying the logs at selected level and all the levels above it:
  - 0-Emergency
  - 3-Error
  - 4-Warning (is the default setting)
  - 6-Info
  - 7-Debug
  For example, if you select 0-Emergency, all the emergency logs are displayed. However, if you select 6-Info, all the logs from 0-Emergency to 6-Info are displayed.
- SIEM
  To select security information and event management (SIEM) that you have configured for forwarding automation logs that are generated.
  Note: The configuration of external SIEM integration is disabled by default. So ensure that you enable it and configure your SIEM server settings correctly if you select SIEM as the server location. For more information, see Configure integration with SIEM.
Use the Log to server action to write custom log messages at any point in your automation. Log messages are stored in the location configured by your administrator. For more information see Log to Server action.