- Getting started
- Best practices
- 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
- SmartCard Authentication
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Managing your host license
- Configuring system email notifications
- Audit logs for the host portal
- Maintenance Mode
- Organization administration
- Troubleshooting
Audit logs
A log is an array of data ordered by time that follows the "first in, first out" rule. That means the oldest log entry is the first one deleted at the end of the retention period. Logs help with debugging issues, increasing security and performance, or reporting trends.
Audit logs are a special type of logs that help to gain insight into events that happened within your organization. It answers the who, when, and where for every event, and it allows you to keep track of important changes.
The Audit Logs page captures actions performed from the Admin pages and log in activity for the organization. This includes user log in activity, license upgrades, any changes made to your tenants, refresh of an API key, and more.
As the organization administrator, you can view the audit logs by going to Admin > Audit Logs in a specific organization.
Upon upgrading to 2021.10 or later, on the Audit Logs page you can see only operations performed after the upgrade. To see operations performed before the upgrade, you need to retrieve the data from the SQL database. For example, use the following query to retrieve user login attempts made prior to the upgrade,
SELECT * FROM [identity].[UserLoginAttempts]SELECT * FROM [identity].[UserLoginAttempts]Audit logs for the Automation Ops service are also displayed in the Admin > Audit Logs page.
For information about the events logged for Automation Ops, see Audit Logs in the Automation Ops documentation.
The audit from the Orchestrator service lists all the events linked to a specific tenant. You can see folders or machines creations, packages uploads, roles assignments, or settings updates. Simply put, every step that may influence the orchestration process is captured inside the Orchestrator's Audit page.
You need to be an Administrator to access the Audit page at the tenant level.
The robot logs found at Orchestrator's folder level are useful to monitor the executions of every robot from a specific folder.
You need the specific folder permission to manage the logs .
