Configure log levels

You can configure operational log levels for individual Automation Orchestrator platform components using the Settings UI or the Settings API, and set a fallback level using an environment variable for components not explicitly configured.

Before you begin

  • You have the platform administrator role in Automation Orchestrator.
  • You have access to the Settings UI or the Settings API.

About this task

Log level changes take effect immediately without restarting pods. The new level applies to all subsequent log events from the configured component. Levels set through the Settings UI or API override the APP_FALLBACK_LOG_LEVEL environment variable for the configured component.

Procedure

  1. Navigate to Settings > Logging > Log Levels.
  2. Select the component and log level, then click Save.
  3. Alternatively, send a PATCH request to the log level API endpoint. 
    $ curl -X PATCH https://orchestrator-host/api/v1/settings/logging/levels \
    -H "Authorization: Bearer token" \
    -H "Content-Type: application/json" \
    -d '{"logger": "component-logger-id", "level": "LOG_LEVEL"}'
  4. Verify the log level change by checking recent log output. 
    $ oc logs deployment/orchestrator-deployment-name -n namespace --since=1m | \
    jq 'select(.logger == "component-logger-id") | {level, message, timestamp}' | head -n 5

Results

The log level for the configured component is updated and takes effect immediately.