- Updated: 2020/01/22
Gather your Automation Anywhere bot logging data in one central location for better and more efficient consumption.
Logging data is generated throughout the Automation Anywhere product. For logging to be more useful, we recommend that you consolidate your logs into one central machine or area.
For additional information about the generated logs, see Auditing and Logging.
Windows built-in logging strategy
Windows has a built-in form of centralized logging. To setup a single machine that pulls all logging data from other machines into a single location using subscriptions:
- Open Event Viewer on the machine to be used for central logging.
- Subscribe to Logging Events from each of the other source computers.
To be practical and useful, logging methods need to: collect logging events across all systems and apps, provide a holistic view of the entire environment, and display the collected logs in a single area or tool. Tools, such as Splunk, aggregate various types of logs from various sources into one central location.
Log event types
There are three event types.
- Infrastructure logging
- Network, router, switch, firewall, gateways, etc.
- Systems logging
- Windows Event Viewer, Web Server Logs, and machine logs.
- Application logging
- Control Room
- Bot Runner
- Bot Creator (Dev Client)
- Credential Vault
- Bot Insight for analytics
How long you retain collected logs is typically determined by company policy, and typically defined in terms of currently active (hot), accessible backup (warm), and historical records (cold).
- Hot storage
- The current, active log files. Stored on the server where they were generated or where they are collected. Keep these files locally, on your servers, for at least a month.
- Warm storage
- Corporate-wide backups that are generally available for at least one year. Typically, are moved from warm storage to cold storage after five years.
- Cold storage
- Long term archive storage such as the use of magnetic tape that survives the test of time. These are the files that are moved from warm storage, five years after origination date.
- Log Rotation by Time
- Create a single new log file per 24 hours.
- Log Rotation by Size
- Create new log file based on the size of the log file.
- Log Rotation by Bot
- Some combination of both to limit size and time per log file.