- About organizations
- Managing organization settings
- Managing notifications
- Activating your Enterprise license
- Upgrading and downgrading licenses
- Requesting a service trial
- Allocating licenses to tenants
- Monitoring license allocation
- License overallocation
- About logs
- Exporting 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.
Cloud Portal and cloud services are using different types of logs to 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.
Automation Cloud Administration
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 > Organization > Audit Logs.
Each audit log entry is kept for approximately 30 days in the case of Community accounts, and for 2 years for Enterprise.
To keep the logs beyond this limit, we recommend to periodically archive them as CSV files to your local storage. Click Download to export the audit logs.
Audit logs for the Automation Ops service are also displayed in the Admin > Organization > 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 audit logs are retained for 6 months in the case of the Community plan, and for 2 years for Enterprise.
To keep your logs beyond these limits, you can export them to your local storage.
Learn more about the audit logs at Orchestrator's 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.
Robot logs are kept for at least 30 days by Orchestrator.
If you need these logs for longer, you can periodically export logs to:
- your local storage
- third-party cloud storage.
For instructions, see Exporting logs.