Skip to main content
Version: Next

Archive Health Dashboard

The Archive Health Dashboard is an admin page that answers one question at a glance: are the archive databases Cortex reads from reachable and responding as they should? It combines a health snapshot of your configured archive sources with live latency measurements of the databases Cortex uses.

Open it from Utilities → Health Check. It requires a Cortex admin account with the Health Check admin right (see Security groups and access control).

What the dashboard shows​

Overall health​

A row of indicators summarises the current state:

IndicatorWhat it tells you
Overall HealthA single verdict - Good, Warning, Bad or Unknown - with a short explanation underneath. It turns Bad when no archive source can be reached or a database health check fails, Warning when an archive source is unavailable, a source reports no archive content, or a database is slower than the health threshold, and Unknown while latency measurements are still running.
Source AvailabilityHow many of the configured archive sources Cortex can currently connect to and enumerate, for example 3 / 3.
Application LatencyThe current average response time measured from the browser application server.
Highest DB LatencyThe slowest database among those measured, with the database's name underneath. Shows Failed if a database health check could not complete.

Health Snapshot​

The Health Snapshot panel breaks the same picture into its parts:

  • An availability ring and a Source Availability bar showing available sources against configured sources.
  • A Content Available bar showing how many sources reported archive content (tables) when Cortex enumerated them. A source that connects but reports no tables is reachable yet empty, which usually means the archive connection points at the wrong database or schema.
  • A Database Responsiveness bar counting how many databases are within Cortex's 100 ms health threshold.
  • Overall Assessment - a plain-language summary of the current state, for example how many sources are available and whether any database latency is above the threshold.
  • Recommended Next Step - what to look at first, such as reviewing a source whose connection failed or a database whose latency is high.

Current Performance​

The Current Performance panel shows a tile per component with its average response time: the Application Server, the Cortex Database, the Cherwell Database (where a Cherwell archive is configured), and every enabled Database data source.

Cortex treats an average database latency above 100 ms as slow. A tile above that threshold is marked Above Cortex health threshold; a tile whose check failed reports Health check failed instead of a time.

System Details​

Below the panels, System Details lists the underlying measurements, each refreshing itself:

  • Memory usage for the application server and SQL Server.
  • Client latency, refreshed every few seconds.
  • A latency check per database: the Cortex database, the Cherwell database where one is configured, and each enabled Database data source.

Refreshing the dashboard​

  • Refresh Dashboard re-computes the snapshot and restarts the live latency measurements.
  • The latency checks in System Details refresh on their own - the client latency every 5 seconds and the database checks every 2 seconds - so the numbers keep moving without any action.

Archive Performance Test​

Where a Cherwell, Ivanti Neurons or Jira archive is configured and licensed, the dashboard also offers Run Archive Performance Test. That opens the separate Archive Health Check page, which runs deeper timed tests against the archive itself. The dashboard is the day-to-day view; the performance test is the detailed measurement you run when something looks slow.

See also​