Troubleshooting: Monitoring charts do not update

News Knowledge Base
, , , ,
1

Why are the charts in the Monitoring tab not displaying transaction or other relevant info?

Issue Description

When accessing the Tenant or folder-level Monitoring tab, one or more charts show only a placeholder image for a given period, while the data indicates that a non-zero volume should be represented. This can occur for any chart: Machines, Processes, Queues, License, and so on.
Charts in the monitoring section display only placeholder images.

Root Cause

Blank charts may result from several scenarios:

  • No data for the filtered period
  • No data for the selected chart type
  • Database timeouts
  • Database deadlocks
  • A database change that results in a dataset returned for a query, when it should be populated.

Validation

The first two scenarios may seem trivial but could be masking other issues. If automations only run during the work week, there may be no data for the past 24 hours at 8 AM on Monday. Select a longer time filter and observe the results. If your organization only processes queue items, there may not be any data for jobs.
The next two scenarios can be identified by errors in the Application Event Viewer Log from the Orchestrator server. See How To Deal With Deadlocks For The Orchestrator Database?

To validate this issue, please share the following:

  1. A screenshot of the Orchestrator interface showing the chart placeholder image and capturing the relevant top-level section, such as the folder or Monitoring tab, applied filters, and Orchestrator URL.

02396181 Monitoring charts with placeholders2.png

  1. Another screenshot showing the chart target over the same period, such as jobs, queue items, or machine details.

02396181 Transaction items in folder over same period 2.png

  1. The Zip output file from this Orchestrator Log Gathering script.
  2. The script collects the following information:
    • Application logs
    • Security logs
    • System logs
    • CAPI2 logs (for certificate issues)
    • Appsettings.Production.json
    • UiPath.Orchestrator.dll.config
    • IIS logs from the last 7 days
    • Output of the Platform Configuration Tool readiness check
    • Network trace (optional, can be enabled during the script execution)
To use the script, run it as an Administrator on the Orchestrator machine.
  • During the execution, specify the Orchestrator installation path; press enter to use the default path.
  • Subsequently, there will be option to initiate a network trace (Note that this can significantly increase the script's runtime).
  • Reproduce the identifiable issue and once done, press enter to continue.
  • The script will then gather all the necessary logs, output the results of the Readiness check, and save everything in an archive. This archive should then be sent back to us for further analysis.