Log view

Logs are created by Management Console and by the database logging of RoboServers. Both Management Console logs and RoboServers logs are written to the logging database.

• The Schedule runs and Schedule messages are Management Console logs that report information on schedules.

• The remaining logs Robot runs, Robot messages, Robot summary, RoboServer messages, DAS messages, and Task messages are RoboServer logs that contain information on the status of RoboServer and on robots and robot runs.

The logging database must be configured in the Management Console settings and the logging cluster settings must be enabled on the RoboServer.

Consider the following about configuring logs and their retention:

• The date format in "Log view" filters depends on the language setting in the Management Console.

  • When set to English, the browser language settings are used to determine the dialect of English.

    For example, if English (United Kingdom) appears at the top of the languages list, the date in the filter is formatted according to the British English standard date format.

  • If no preference is set in the browser settings, English (United States) is the default. See also Log layout.

• Set the retention policy for your logs in the RoboServer log database by specifying a number of days to keep the logs and the number of messages in the robot run.

  The logs are cleaned daily by deleting the oldest messages first. The default values are 10 days and 500 messages.

• For robots, all thrown exceptions are logged as robot errors.

• For Robots called from Basic Engine Robots, the exceptions are returned to the Call Robot step, and the configuration of the Call Robot step determines if the error is logged.

• For Basic Engine Robot step error handling, set the following options:

  • Ensure that the Log as Error option is enabled for all steps that you need to log errors for.

  • In Design Studio, in the step properties, on the Error Handling tab, verify that Log as Error is selected.

  • If using the RQL API and you want step errors to be returned over the API and logged in the Management Console, ensure that the API Exception option on the Error Handling tab is selected.

The page layout for each log is identical, but you can change the way the information for each log is presented:

• Filter the lists of messages in the table by applying filters in the Filter text field. When you click the filter icon, the "Column filters" dialog box appears with a number of filter options. See also Filtering.

  For example, depending on the log type, you can filter by projects, a time frame, total execution time, execution result, severity of error messages, and so on.

• Use the Orphan check box to filter out orphan records that remain when a project is removed, but the log entries related to it are not removed.

• Select the table columns to display for a log using the menu icon on the right.

• Refresh the displayed information by clicking the refresh icon on the right.

• Reset the custom column settings by clicking the reset icon on the right.

• Change the display order column entries by clicking the icon next to the column label.

• Select the number of items to display per page and navigate among pages by using the navigation menu in the bottom right corner. If there are more results than the number selected per page, navigate to the next page using the controls under the data grid.

When you select a column heading, the heading changes color to indicate it is the active column.

Also, when you select a row, the row becomes highlighted. You can highlight multiple rows.

For messages in the Log view, the Severity column displays a severity level based on logging events and filters.

When selecting a value in the Severity filter, note that the result will be greater or equal to the selected value. For example, if you set the Severity filter to Warning, the result contains errors, apart from warnings.