Skip to main content

Logs

The Logs tab in the AutomatR Orchestrator application provides users with a comprehensive view of the logs generated during the execution of automation processes. These Logs are essential for monitoring and troubleshooting automation tasks, as they offer valuable insights into the execution steps, errors, and other relevant information. The Logs tab is designed to facilitate easy access and analysis of logs from various perspectives. You can review and analyze log data to identify potential issues, measure performance, and ensure compliance with your organization's requirements. Here's a detailed explanation of the sections and options available in the Logs tab:

FieldDescription
Bot NameThe Bot Name section displays the names of the bots that executed the automation processes. Each log entry is associated with a specific bot responsible for performing the task.
Log LevelThe Log Level section indicates the level of verbosity or detail recorded in the logs. Log levels categorize log entries into four different levels of significance, such as: Verbose, Debug, Information and Error.
For more details, refer the below Search >> Log Level section.
Time StampThe Time Stamp section shows the date and time when each log entry was generated. The timestamp helps in tracking the sequence of events during the automation process execution.
MessageThe Message section contains the detailed log messages, providing information about the events, actions, and outcomes of the automation process.
ProcessThe Process section displays the name of the automation process associated with each log entry. It helps users identify which process the log pertains to, especially in scenarios with multiple concurrent processes.
Machine/Windows IdentityThe Machine/Windows Identity section shows the identity or name of the machine or user account from which the automation process was executed. This information is particularly useful in a multi-machine environment to track execution origins.
SearchThe search functionality in the Logs tab enables users to find specific logs quickly. Users can enter search terms in the search bar to filter the list of logs based on bots, log level or dates.

Option Description
Bot The search option by Bot allows users to filter logs based on specific bots, making it easier to focus on the logs generated by particular bots.
Log Level The Search by Log Level dropdown feature enhances the log filtering capability by allowing users to search and view logs based on specific log levels. Log levels categorize logs according to their importance and level of detail, enabling users to focus on specific types of log entries that are relevant to their analysis or troubleshooting needs.
  • The Verbose log level is the most detailed and comprehensive level of logging. It provides an extensive record of events, actions, and states during the execution of an automation process. Verbose logs capture a high level of detail and are typically used for in-depth debugging and troubleshooting complex issues.
  • The Debug log level is used for more granular logging than the Information level. Debug logs capture specific details and events that are relevant to diagnosing and debugging issues during the automation process. Debug logs offer a focused view of the execution flow and are often used during development and testing to understand the step-by-step behavior of the automation tasks.
  • The Information log level represents general, non-critical information about the automation process. Information logs include status updates, significant events, and other relevant messages that provide a high-level overview of the process execution. This log level serves as a balance between verbosity and essential information, offering a concise view of the automation process's progress and outcomes.
  • The Error log level signifies critical issues or errors encountered during the automation process. Error logs capture events or conditions that require attention and resolution. These logs help identify issues that may affect the correct execution of the process or result in undesired outcomes. Error logging is vital for troubleshooting and identifying potential bottlenecks or flaws in the automation flow. These logs are usually monitored closely by administrators and developers to promptly address critical errors and ensure the successful execution of automation tasks.
The Search by Log Level feature offers users a valuable tool for filtering logs based on their level of importance and detail. By selecting a specific log level, users can streamline their log analysis, focus on relevant information, and efficiently troubleshoot automation processes, leading to improved performance and smoother operations.
Dates The Search by Dates option provides users with powerful date filtering capabilities, enabling them to narrow down logs based on specific time periods. This feature offers a variety of predefined date ranges and the option to select a custom range, facilitating precise log analysis and troubleshooting.
  • Today: Displays logs that were generated on the current date. This option is useful for real-time monitoring and tracking of automation processes executed on the same day.
  • Yesterday: Presents logs generated on the previous day. It allows users to review logs from the previous day's automation activities and investigate any issues that may have occurred.
  • Last 7 days: Displays logs from the past seven days, including the current day. This range is ideal for analyzing recent logs over the past week.
  • Last 30 days: Shows logs from the last 30 days, including the current day. Users can use this range for more extended historical analysis, observing changes over a month.
  • This month: Displays logs generated during the current calendar month. This option offers a concise view of logs for the ongoing month.
  • Last month: Provides logs from the previous calendar month. Users can utilize this option to review logs from the prior month's activities and identifying long-term patterns.
  • Custom range: Allows users to define a specific time range by selecting a start date and end date from a calendar or date picker. Users can input precise dates to focus on logs generated within their desired time frame, which may not align with the predefined ranges.
Auto-ReloadThe Auto-Reload option is a user-configurable setting that determines how frequently the log table is automatically refreshed with the latest log entries. This feature provides users with the convenience of real-time updates without the need to manually refresh the page. Users can choose from a range of pre-defined time intervals for auto-reloading the logs table.
  • Off: Selecting the Off option disables the auto-reload feature. When this option is chosen, the log table will not refresh automatically, and users will need to manually refresh the page to view the most recent log entries. This option is ideal when users prefer to control the refresh themselves, especially when working with static data or conducting detailed analysis.
  • 5 sec: The 5 seconds option sets the auto-reload interval to five seconds. Every five seconds, the log table will refresh, displaying any new log entries generated during that period. This option is suitable for users who require near-real-time updates and want to monitor automation activities with minimal delay.
  • 10 sec: The 10 seconds option refreshes the log table every ten seconds. It provides a slightly longer interval compared to the 5-second option, balancing real-time updates with reduced auto-reload frequency for users who require updates at regular intervals.
  • 15 sec: With the 15 seconds option, the log table will automatically refresh every fifteen seconds. This setting offers a moderate auto-reload frequency, suitable for users who need timely updates without excessive page refreshes.
  • 30 sec: Selecting the 30 seconds option sets the auto-reload interval to thirty seconds. The log table refreshes at this time interval, providing updates at regular intervals without causing excessive page reloads.
  • 60 sec: The 60 seconds option refreshes the log table every sixty seconds or one minute. It offers a more extended interval between refreshes, making it suitable for users who require periodic updates without frequent interruptions.
  • 120 sec: The 120 seconds option sets the auto-reload interval to two minutes. With this setting, the log table refreshes every two minutes, providing updates at more extended intervals, suitable for users who require periodic monitoring without real-time requirements.
The Auto-Reload option empowers users to customize the log table's refresh behavior according to their monitoring and analysis requirements. By choosing an appropriate auto-reload interval, users can efficiently monitor automation activities, stay up-to-date with log entries, and respond promptly to critical events, ensuring seamless operation of their automation processes.
Download to ExcelThe Download to Excel option allows users to export the logs data in Excel format. This enables further analysis, data processing, or reporting outside of the AutomatR Orchestrator application.

The Logs tab in the Orchestrator application offers a user-friendly interface for accessing and analyzing log data from automation processes. With various search options, auto-reload settings, and advanced search capabilities, users can efficiently navigate through logs, troubleshoot issues, and monitor the performance of automation tasks. The ability to download logs to Excel further enhances data management and reporting capabilities. Overall, the Logs tab plays a crucial role in ensuring smooth and reliable automation operations by providing valuable insights into the execution of processes.