- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Classic Robots
- Troubleshooting
Managing Logs in Orchestrator
Beyond the Logs page you can also view robot-specific and job-specific logs.
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
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.
AND
operator between them. For example, if you only want to see logs named "sent file", you would enter "sent AND file".
From the Robots page, for an indicated Robot:
-
click the corresponding More Actions button, and then View Logs
Note:If you edit the Robot name, the messages logged with the previous Robot name are no longer displayed.
For Cloud Platform-based Orchestrator services, Robot logs are only kept for 30 days.