- Getting started
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- Enforcing user-level Integration Service connection governance
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Resource Catalog Service
- Automation Suite Robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Monitoring
- Queues
- Assets
- Storage Buckets
- Indexes
- Orchestrator testing
- Integrations
- Troubleshooting
Orchestrator user guide
Managing Logs in Orchestrator
Viewing Logs
The Logs page displays the logs for all processes and jobs in your folder.
You can use filters to narrow down the log list by various criteria, or you can use the search field to look for specific logs by name.
By default the Logs pages only display events from the previous day. You must manually change the Time filter to see earlier events.
You can access the logs for a specific job or process either from the Logs page, or from the Jobs page.
Searching for logs by name
The following information only applies when using Elasticsearch.
You can use the search field to look for specific logs by their name.
One-word search
Entering one word in the search field displays only logs whose name includes that particular word. For example, if you search for "file", you are returned all logs called "file", as well as all logs which include the word "file" in their name.
Multiple-word search
By default, the search field applies an OR operator when multiple words are used. As such, if you enter "sent file", you are returned logs called "sent file", as well as all logs containing the term "sent" or "file" in their name.
To display only logs whose name exactly matches the words entered in the search field, you need to add the AND operator between them. For example, if you only want to see logs named "sent file", you would enter "sent AND file".
If the log name contains a - symbol, you must replace it with AND when you perform a search.
Job specific Logs
From the Jobs page, for an indicated job:
- Select the corresponding More Actions button.
- Select View Logs, to display the list of all logs for the selected job.
From the Logs page, for an indicated job:
- Select the corresponding More Actions button.
- Select View all logs for this job, to display the list of all logs for the same job.
Process Specific Logs
From the Jobs page, for an indicated job:
- Select the corresponding More Actions button.
- Select View all logs for this process, to displays the list of all logs for the parent process, across all executed jobs.
From the Logs page, for an indicated job:
- Select the corresponding More Actions button.
- Select View all logs for this process, to displays the list of all logs for the parent process, across all executed jobs.
Figure 1. Accessing logs from the Jobs page
Figure 2. Accessing logs from the Logs page
Exporting Logs
Regardless from where you open the Logs page, you can export the data to a.csv file, by clicking the Export button.