Despite the configuration of process retention being set to 180 days in Orchestrator, the log retention policy is limited to 30 days. Retaining jobs for 180 days without corresponding robot logs serves limited purpose.
Retention Period Discrepancy Between Jobs and Robot Logs in Automation Cloud Orchestrator
In Automation Cloud Orchestrator, the retention period for process data and logs can be configured to ensure that necessary information is available for audits, reviews, and troubleshooting. However, there seems to be a discrepancy between the retention period for jobs (set to 180 days) and the retention of robot logs (which is only 30 days). Let's clarify both points:
Retention Period Discrepancy
- Configured Job Retention (180 Days):
- This setting ensures that the details and outcomes of jobs are retained for up to 180 days. This includes information such as job status, execution times, and other metadata
- The purpose of retaining jobs for a longer period is to maintain a historical record of automation activity, which can be useful for performance analysis, compliance, and audit purposes.
- Robot Log Retention (30 Days):
- Robot logs contain detailed logs generated by robots during the execution of processes. These logs include information about the steps taken, any errors encountered, and other diagnostic details.
- The 30-day retention for robot logs is typically set to manage storage costs and performance since these logs can be voluminous.
Purpose of Retaining Jobs Without Logs:
Retaining job details for 180 days without the corresponding robot logs might seem counterintuitive, but it serves specific purposes:
- Audit Trails: Even without detailed logs, job records provide an audit trail, showing when and what jobs were executed, their outcomes, and which robots were involved
- Performance Monitoring: Analysis of job metadata over a longer period can help identify trends, optimize processes, and improve resource allocation
- Compliance and Reporting: Some regulatory or internal policies might require keeping job records for a certain period, even if detailed logs are not available.
Reviewing Logs Manually from Exported Location
To review logs manually when needed, even after the 30-day retention period, consider the following steps:
- Export Logs Regularly: Set up a routine to export logs before they are purged. This can be done by configuring automated scripts or using Orchestrator’s built-in features to periodically export logs to an external storage location.
- Use External Storage Solutions: Store exported logs in a secure, searchable external storage system such as a database, cloud storage service, or a log management solution like Splunk, ELK Stack, or Azure Log Analytics.
- Accessing and Reviewing Exported Logs: To review logs, access the external storage where the logs are saved. Use search and filtering capabilities provided by the storage solution to locate specific logs based on timestamps, job IDs, or other relevant criteria.
Conclusion:
The 180-day job retention ensures that key job-related data is available for audits and performance reviews, while the 30-day log retention balances storage use and performance. To manage this effectively, regularly export and store logs externally where they can be accessed as needed for detailed reviews and troubleshooting.