Monitor visualized log data on a predefined dashboard

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read

    • Use visualizations to monitor log data on the built-in Operational Dashboard in Service Operations Workspace Log Analytics and address issues as they occur in the system.

    Before you begin

    Role required: evt_mgmt_operator or viz_admin

    Important:
    From the Vancouver release onward, this feature is deprecated and replaced with the AIOps HLA Operational dashboard. For more information about AIOps dashboards, see AIOps Dashboards in Service Operations Workspace for ITOM. You can also build a custom dashboard per your needs. For more information, see Create log data dashboards and visualizations.

    Procedure

    1. Open the Log viewer using one of the following methods:
      • Navigate to Workspaces > Service Operations Workspace and select the Log Viewer icon (Log viewer icon.).
      • While viewing log entries for an alert on the Surrounding logs tab, select Log viewer.
    2. Select the selection icon at the top right of the Log viewer tab, and then choose Manage my dashboards from the drop-down list.
      The Operational Dashboard tab displays.

      By default, the dashboard visualizes log data that was ingested in the last 24 hours.

      Operational dashboard.

    3. Optional: Change the time range for which data is shown by selecting the required range from the Date drop-down.
      You can specify a custom range by selecting Custom and then selecting the required start and end dates.
    4. Monitor the visualized log data and use it to identify and address issues.
      Table 1. Operational Dashboard
      Name Description How to use the data
      Logs processed The number of logs that were processed and analyzed in the selected period. Ensure that the log data is streaming as expected.
      Logs per Application Service The number of logs streamed for each application service in the selected period. Ensure that log data is streaming as expected for each application service.
      Error rate per Application Service The number of logs with errors for each application service in the selected period.
      Note:
      Health Log Analytics automatically creates alerts for Error anomalies.
      		 Identify errors in the logs.
      Logs per Host The number of processed logs for each host in the selected period. Identify hosts that are logging more data, or less data, than expected.
      Error rate per Component The number of logs with errors for each component in the selected period. Ensure that the components have a normal Error rate.
      Severity rate The severity level rate of the logs for the streaming sources. Ensure that Critical and Error level rates are as expected.