View operational system logs for troubleshooting

In the Automation Orchestrator web console, click Observability > Operational Logs.

The log viewer displays the most recent operational log entries, sorted by timestamp in descending order.

Use the following filter criteria:

• Time range — set start and end timestamps to scope the view to the period when the issue occurred.
• Severity level — filter by severity (DEBUG, INFO, WARNING, ERROR, CRITICAL) to isolate errors and warnings.
• Component or service name — filter by the source_component field to view logs from a specific platform service, such as syntara.execution or syntara.api.
• Keyword search — enter a text string to search across log messages for specific error codes, exception names, or resource identifiers.

The following patterns appear frequently in operational logs:

• Service errors — entries with severity ERROR or CRITICAL that include exception stack traces or error codes. These entries indicate a service failure that may require administrator intervention. Check the source_component field to identify the affected service.
• Resource exhaustion warnings — entries with severity WARNING that reference memory limits, disk space, CPU throttling, or connection pool exhaustion. These entries appear before a service outage and indicate that the platform is approaching capacity limits.
• Connectivity failures — entries that reference connection timeouts, DNS resolution failures, or TLS handshake errors when communicating with external services such as LLM providers, Ansible Automation Platform, or identity providers. Check the target hostname and port in the log message to identify the unreachable service.

After identifying an error or warning, expand the time range slightly to view log entries immediately before and after the event. Preceding entries often reveal the triggering condition, and subsequent entries show whether the platform recovered or the error persisted.