Uptime Monitoring: Dashboard

Overview

Use this page to monitor the real-time health and availability of configured uptime checks. The dashboard aggregates results from all active checks into six KPI summary cards — Total Checks, Healthy, Degraded, Unhealthy, Open Incidents, and Overall Uptime — so you can assess service availability at a glance without navigating into individual check records.

Uptime checks are created and configured on the Uptime Monitoring: Checks page. The dashboard consumes those check results and surfaces incidents, which are tracked in full on the Uptime Monitoring: Incidents page. When response-time thresholds cause a check to enter a Degraded or Unhealthy state, the Open Incidents counter increments and an incident record is written automatically.

On this page you can filter the displayed checks by period, environment, service type, and tenant; refresh data on demand or automatically; and expand individual check cards to view inline analytics or enable and disable specific checks without leaving the dashboard.

Key concepts

• uptime check - A configured probe that tests a specific endpoint at a regular interval using a defined protocol (for example SSH Banner or REST API). Each check produces a status classification, a response-time measurement, and an uptime fraction on every poll cycle. (related: Uptime Monitoring: Checks)
• check status - The current health classification of a check: Healthy (all recent polls succeeded within thresholds), Degraded (polls are succeeding but response times are elevated), or Unhealthy (polls are failing). Status is shown as a color-coded badge and border on each check card. (related: Uptime Monitoring: Incidents)
• incident - An automatically created record that tracks a period during which a check entered a Degraded or Unhealthy state. An incident remains open while the condition persists and is resolved when the check returns to Healthy. (related: Uptime Monitoring: Incidents)
• service type - The protocol or method the check uses to probe the endpoint, such as SSH Banner, REST API, SMTP, DNS, or certificate validation. The Service Type filter on this page narrows the dashboard to checks of one protocol family. (related: Uptime Monitoring: Checks)
• uptime fraction - The ratio of successful polls to total polls in the selected period, displayed as both a percentage and a count in parentheses (for example 99.97% (2879/2880)). It measures how often the endpoint was reachable during the window.

When to use it

• Checking at a glance whether all monitored services are Healthy before or after a deployment.
• Identifying which specific checks contributed to an elevated Open Incidents count.
• Filtering by environment or tenant to assess availability for a specific segment of your infrastructure.
• Temporarily disabling an individual uptime check during planned maintenance without navigating to the Checks configuration page.
• Reviewing the license usage banner to determine how many of your licensed endpoint slots are consumed.
• Spotting slow-responding endpoints by comparing color-coded last-response times across check cards.

Before you begin

• At least one uptime check must be configured. If none exist, the Check Status Overview section shows a 'Create your first check' link instead of check cards. Configure checks on the Uptime Monitoring: Checks page.
• Your account must have access to the Uptime Monitoring module. If the navigation section is absent, contact your administrator to verify your permissions.
• If checks are scoped to specific tenants, the Tenant filter enumerates only the tenants associated with your account's access level.

Common workflows

Assess service availability across environments

Persona: Load-test operator or on-call engineer

1. Open the Uptime Monitoring Dashboard by selecting Uptime in the platform navigation.

- Expect: The page loads showing six KPI cards, a license usage banner, and the Check Status Overview grid with one card per configured check.

2. Select the target environment from the Environment dropdown, for example Production.

- Expect: The KPI cards and check cards reload to show only checks tagged with that environment; checks from other environments are removed from view.

3. Review the Unhealthy and Degraded KPI cards; if either is greater than zero, locate the affected check card by its amber or red top border in the Check Status Overview.

- Expect: Affected cards are visually separated from Healthy cards by border color, making them easy to identify without reading every status label.

4. Select the Analytics toggle on an affected check card to expand the inline Analytics: sub-panel.

- Expect: A chart area appears below the card's summary row showing historical response-time and uptime data for the selected period.

Verify: All monitored check cards show a green border and a Healthy status label. The Degraded and Unhealthy KPI counters both display 0. If an incident was expected to have resolved, the Open Incidents counter also displays 0.

Pause a check during planned maintenance

Persona: Administrator

1. Locate the check card for the endpoint undergoing maintenance in the Check Status Overview.

- Expect: The card is visible with its current status badge, uptime fraction, and last response time.

2. Select the Enable / Disable toggle on the check card to disable polling.

- Expect: The check's enabled state changes on the server; no new poll results or incidents are generated for that endpoint, and the KPI counters update on the next refresh.

3. After maintenance completes, select the Enable / Disable toggle again to re-enable the check.

- Expect: Polling resumes at the next scheduled interval and the Last check timestamp on the card begins to advance again.

Verify: The check card returns to an active state with a Last check timestamp that updates on each poll cycle. The Overall Uptime figure stabilizes as post-maintenance successful polls accumulate.

Steps

Step 1

Navigate to the Uptime Monitoring Dashboard by selecting Uptime in the platform navigation.

Expected result: The dashboard loads displaying six KPI summary cards across the top row (Total Checks, Healthy, Degraded, Unhealthy, Open Incidents, Overall Uptime), a license usage banner showing the fraction of licensed endpoint slots in use, and the Check Status Overview grid with one card per configured endpoint. Each card shows the check name, a service type badge, a color-coded Healthy or Degraded or Unhealthy label, the uptime percentage and poll fraction, the last response time in milliseconds, the environment, an optional tenant row, and the last check timestamp.

Reviewing the KPI row and check cards together gives you the full picture needed to decide whether any endpoint requires immediate attention or investigation.

• The Period dropdown defaults to Last 24 Hours; changing it recalculates uptime fractions and incident counts for all cards in the new window.
• The Environment, Service Type, and Tenant dropdowns all default to showing all items; combine them to narrow the dashboard to a specific slice of your infrastructure.
• The Auto checkbox is unchecked by default; enable it so the page refreshes automatically instead of requiring a manual Refresh click.
• Check card top borders are color-coded: green for Healthy, amber for Degraded, red for Unhealthy — allowing you to identify problems before reading any text.
• The license usage banner shows a progress bar and a percentage; if the fraction is close to your licensed limit (30 endpoints in the example environment), review the Uptime Monitoring: Checks page to disable checks that are no longer needed.

Field reference

| Field | Purpose | Format / Validation | Required | Default |

|---|---|---|---|---|

| Period | Sets the time window over which uptime fractions, incident counts, and response-time history are calculated. A shorter window (Last 24 Hours) shows the most recent performance and excludes older incidents; a longer window reveals trends and past degradations useful for SLA reporting. Use shorter periods for live operational monitoring and longer periods for historical review. | Dropdown | No | Last 24 Hours |

| Environment | Filters the Check Status Overview and KPI cards to show only checks tagged with the selected environment. Use this to isolate Production checks from Staging or other environments when assessing live-service health. | Dropdown | No | All Environments |

| Service Type | Filters the dashboard to checks of a specific protocol family. The list is populated dynamically from the check types present on the appliance (for example SSH Banner, REST API, SMTP, DNS). Use this to compare response times or uptime for a single technology independently of others. | Dropdown | No | All Service Types |

| Tenant | Narrows the dashboard to checks scoped to a specific tenant. When a check is not associated with a particular tenant, the Tenant row does not appear on its card. Use this in multi-tenant deployments to view availability for a single customer segment. | Dropdown | No | All Tenants |

| Auto | When checked, the dashboard refreshes data automatically at a regular interval so KPI cards and check cards stay current without manual clicks. When unchecked, the page updates only when you click Refresh. Enable Auto during live incident response to watch status changes in real time; leave it unchecked when examining a fixed historical snapshot to prevent the period from shifting. | Checkbox | No | unchecked |

Column reference

| Column | What it shows | How to read it |

|---|---|---|

| Total Checks | Reports the count of all configured uptime checks that match the current filter combination. | The count reflects checks visible under the current Period, Environment, Service Type, and Tenant filters; changing any filter updates this number. |

| Healthy | Reports the count of checks currently in a Healthy state within the filtered set. | A value equal to Total Checks means all monitored endpoints are within normal response-time and availability thresholds. |

| Degraded | Reports the count of checks in a Degraded state — polling is succeeding but response times are elevated above the lower threshold (approximately 200 ms) without exceeding the upper threshold. | Any value above 0 indicates at least one endpoint is slow. Expand the affected check card's Analytics panel to assess whether the slowness is sustained or a transient spike. |

| Unhealthy | Reports the count of checks that are actively failing polls. | Any value above 0 signals an outage. Navigate to Uptime Monitoring: Incidents for the full incident record and resolution history. |

| Open Incidents | Reports the count of incident records that are currently open (not yet resolved) across all filtered checks. | An open incident exists for each check that entered a Degraded or Unhealthy state and has not returned to Healthy. A value of 0 confirms no active degradation is tracked. |

| Overall Uptime | Reports the aggregate uptime percentage across all filtered checks for the selected period. | 100.0% means every poll across every filtered check succeeded during the period. Values below 95% are styled in amber, indicating significant cumulative downtime in the selected window. |

| Uptime (check card) | Shows the uptime percentage and raw poll fraction for an individual check in the selected period. | The fraction shows how many polls succeeded out of the total polls attempted. A denominator that seems low relative to the period may indicate the check was disabled for part of the window. |

| Last response (check card) | Shows the most recent response time recorded for the check. | Amber coloring signals a response that is slower than normal but not yet failing. Green confirms the endpoint responded within expected thresholds. The HTTP status code (for example 200) confirms the server returned a success response, not just a TCP connection. |

| Environment (check card) | Shows the environment tag assigned to the check, for example Production. | Use this to confirm you are looking at the correct environment when filters are set to All Environments. |

| Tenant (check card) | Shows the tenant the check is scoped to. This row appears only on checks that are associated with a specific tenant; it is absent on checks that monitor shared or unscoped endpoints. | If the row is missing, the check is not scoped to any individual tenant. |

| Last check (check card) | Shows the date and time of the most recent completed poll for the check. | If the timestamp is significantly older than the current time, the check may be disabled, its polling interval is long, or the agent responsible for polling is unreachable. |

Controls reference

Refresh

Immediately reloads all dashboard data, updating the six KPI cards, the license usage banner, and every check card with the latest poll results for the selected period and filters.

When to use: Use when Auto is unchecked and you want a single on-demand update, or when you suspect the displayed data is stale after a recent configuration change.

Side effects: Read-only data fetch; no checks are modified. The 'Updated X ago' timestamp resets to reflect the new load time after the request completes.

Auto

Toggles automatic periodic refresh of the dashboard on or off.

When to use: Enable during live incident response or active monitoring shifts so the page stays current without manual interaction.

Side effects: When enabled, the page refreshes automatically at a fixed interval; the 'Updated X ago' counter advances and resets on each cycle. When disabled, the counter stops advancing until you click Refresh. This control does not modify any check data.

Toggle Analytics (per check card)

Expands or collapses the Analytics sub-panel beneath an individual check card, revealing inline charts for that check's historical response time and uptime trend over the selected period.

When to use: Use when you need to examine the performance trend of one specific check without navigating to a separate analytics page.

Side effects: Read-only; expands or collapses the inline chart area within the card. No data is modified and other cards are not affected.

Enable / Disable check (per check card)

Toggles the enabled state of the uptime check directly from the dashboard card, pausing or resuming polling for that endpoint.

When to use: Use to temporarily pause a check during planned maintenance or a known outage without navigating to Uptime Monitoring: Checks. Re-enable it when the maintenance window ends.

Side effects: Mutating: changes the check's enabled state on the server. A disabled check stops generating new poll results and incidents. Re-enabling resumes polling from the next scheduled interval. The KPI counters update to reflect the change on the next refresh.

Collapse (per check card)

Collapses an expanded check card (one with its Analytics sub-panel open) back to the default compact card view.

When to use: Use after reviewing inline analytics to tidy the dashboard and restore a full view of all check cards.

Side effects: Read-only; collapses the card's expanded content. No data is modified.

Create your first check

Navigates to the Uptime Monitoring: Checks page where you can configure a new uptime check.

When to use: Visible only when no checks have been configured. Use it to bootstrap monitoring directly from the empty dashboard state.

Side effects: Read-only navigation; no data is created on the dashboard itself. The check is created on the destination page.

Verify the result

When the primary task succeeds, the Uptime Monitoring Dashboard displays all configured check cards with green top borders and Healthy status labels, and both the Degraded and Unhealthy KPI counters show 0. The Overall Uptime percentage reflects full availability for the selected period and the Open Incidents counter shows 0 if no incidents are active. The 'Updated X ago' timestamp near the Refresh button confirms the data is current. If any check card shows an amber or red border, expand its Analytics: sub-panel to review the response-time trend and determine whether the degradation is sustained. If the Check Status Overview is empty and shows the 'Create your first check' link, no checks have been configured yet — use that link or navigate to Uptime Monitoring: Checks to add one.

Troubleshooting

• Symptom: The Check Status Overview is empty and shows 'Create your first check' instead of check cards. Fix: Navigate to Uptime Monitoring: Checks and configure at least one uptime check; the dashboard populates once the first check completes a poll cycle.
• Symptom: The Unhealthy or Degraded KPI counter is elevated but you cannot locate the affected check card. Fix: Clear the Environment, Service Type, and Tenant filters by setting each back to 'All' so no checks are excluded from the Check Status Overview.
• Symptom: The Overall Uptime percentage is lower than expected even though all cards currently show Healthy. Fix: Change the Period dropdown to a shorter window; a longer period includes past incidents that drag the aggregate percentage down even after all checks have recovered.
• Symptom: A check card's last-response time is shown in amber. Fix: Amber indicates a response time above approximately 200 ms but still within the acceptable ceiling; expand the card's Analytics: sub-panel to determine whether the slowness is sustained or a transient spike before treating it as an incident.
• Symptom: The license usage banner shows a percentage close to 100%. Fix: Open Uptime Monitoring: Checks and disable or delete any checks that are no longer needed, or contact your administrator to increase the licensed endpoint allocation.
• Symptom: KPI card values do not update after clicking Refresh. Fix: Verify that the Period filter covers the interval in which new polls are expected; if the period ends in the past, data will appear static until you select a window that includes the current time.

Related articles

• Prerequisite: Uptime Monitoring: Checks - checks must be configured there before the dashboard has any data to display
• Next step: Uptime Monitoring: Incidents - open incidents surfaced by the Open Incidents KPI card are investigated and resolved on this page
• See also: Uptime Monitoring: Maintenance - schedule planned downtime windows to suppress false incidents during maintenance instead of manually toggling checks on the dashboard
• See also: Uptime Monitoring: Reminders - configure credential-expiry reminders that appear as banners on the dashboard when certificates or credentials are nearing expiry
• See also: Service Levels: Dashboard - correlate uptime availability data with SLA objectives tracked in the Service Levels module