Uptime Monitoring: My dashboard

Updated

Uptime Monitoring: My dashboard

Overview

Use this page to review the health, uptime percentage, and open incidents of all your configured uptime checks in one place. An uptime check is a monitor that periodically tests whether a specific service or endpoint responds correctly, using a method such as TCP Port, ICMP Ping, or HTTP. Without a single summary view, spotting which of many checks has degraded, and for how long, would mean opening each check individually.

Checks themselves are created and configured on the Uptime Monitoring: Checks page; this dashboard only reads and summarizes the data those checks produce. When a check fails repeatedly, it opens an incident, which you investigate further on the Uptime Monitoring: Incidents page. The credential and license information surfaced here come from Configuration: Credential Profiles and your platform license respectively.

From this page you can filter the summary by time period, environment, service type, and tenant, read KPI totals for healthy, degraded, and unhealthy checks, and scan a status grid of every check with its uptime percentage, last response time, and incident count. Banners call out credentials nearing expiry and how much of your licensed endpoint capacity is in use.

Key concepts

  • uptime check - A configured monitor that periodically tests whether a specific service or endpoint responds correctly, using a method such as TCP Port, ICMP Ping, or HTTP. (related: Uptime Monitoring: Checks)
  • incident - A continuous period during which a check reports a non-healthy status. It stays open until the check recovers or you resolve it. (related: Uptime Monitoring: Incidents)
  • service type - The protocol or method a check uses to reach its target, such as TCP Port, ICMP Ping, or HTTP. It determines how the check decides whether a response counts as healthy. (related: Uptime Monitoring: Checks)
  • licensed endpoint - One unit of your uptime license consumed by each active check. The dashboard shows how many of your licensed endpoints are currently in use. (related: Infrastructure: Licensing)
  • credential - Stored authentication material that some checks need to reach their target. The dashboard warns when a credential used by a check is close to expiring. (related: Configuration: Credential Profiles)

When to use it

  • At the start of a shift or incident review, to get a single-screen view of overall service health.
  • To confirm whether a specific environment or tenant is affected before you escalate a problem.
  • To check how many of your licensed endpoints are still available before creating new checks.
  • To catch credentials that are about to expire before they cause check failures.
  • To spot which checks currently have open incidents and jump into the Incidents page for detail.

Before you begin

  • At least one uptime check must exist, or the dashboard has nothing to summarize; checks are created on the Uptime Monitoring: Checks page.
  • Your account needs access to the Monitoring and Uptime module to view this page.
  • If you plan to filter by environment, tenant, or service type, those classifications must already be set on the checks you want to find.

Common workflows

Review overall uptime health

Persona: load-test operator or admin

  1. Open the Uptime Monitoring Dashboard from the Monitoring and Uptime area.
    • Expect: The KPI cards (Total Checks, Healthy, Degraded, Unhealthy, Open Incidents, Overall Uptime) and the Check Status Overview grid load with current figures and an Updated timestamp.
  2. Review the Unhealthy and Open Incidents KPI cards.
    • Expect: You see at a glance how many checks are currently failing and how many incidents are open.
  3. Select the Refresh button if the Updated timestamp looks stale.
    • Expect: The dashboard reloads and the Updated timestamp resets to a few seconds ago.

Verify: The KPI cards and check grid show current data, confirmed by a recent Updated timestamp and Unhealthy/Open Incidents counts that match the colored check cards below.

Narrow the dashboard to one environment or service type

Persona: load-test operator or admin

  1. Select the environment you want to isolate, for example the one running your Octans quarter-close burst test scenario, in the Environment filter.
    • Expect: The KPI cards and Check Status Overview grid recalculate to show only checks tagged with that environment.
  2. Select an option other than All Service Types in the Service Type filter.
    • Expect: The grid narrows further to checks using only that protocol, for example TCP Port.
  3. Review the filtered Check Status Overview grid for Unhealthy checks.
    • Expect: Only checks matching both filters are listed, making it easier to spot a localized problem.

Verify: The Total Checks and Overall Uptime KPI values change to reflect only the filtered subset, confirming the filters applied.

Steps

Step 1

Open the Uptime Monitoring Dashboard from the Monitoring and Uptime area.

Expected result: The dashboard loads with KPI cards for Total Checks, Healthy, Degraded, Unhealthy, Open Incidents, and Overall Uptime, followed by the Check Status Overview grid listing each configured check with its status, uptime percentage, last response time, and incident count.

This is the first screen to check for a single-page view of your uptime checks' current health before drilling into a specific check or incident.

  • A banner warns when credentials used by your checks are expiring soon, with a View all link.
  • A license usage bar shows how many of your licensed endpoints are currently in use.
  • Each check card's colored left border flags its status; red indicates Unhealthy. Uptime Monitoring: My dashboard - step 1

Field reference

Field Purpose Format / Validation Required Default
Period selector Sets the time window the KPIs and uptime percentages are calculated over. A shorter window such as Last 24 Hours surfaces a recent degradation faster; a longer window smooths out brief blips but can keep the Overall Uptime percentage depressed for longer after a single past outage. dropdown No Last 24 Hours
Environment filter Restricts the dashboard to checks tagged with a specific environment, so you can isolate, for example, production from staging. Select All Environments to see every check at once. dropdown No All Environments
Service Type filter Restricts the dashboard to one check method. The list is populated dynamically from the service types actually used by your checks, so options such as TCP Port, ICMP Ping, HTTP, or others like SMTP, FTP, DNS, or certificate checks only appear once a check of that type exists. Use it to triage all checks of one protocol at once, for example after a network change that only affects TCP. dropdown No All Service Types
Tenant filter Restricts the dashboard to checks belonging to one tenant in a multi-tenant deployment. Use All Tenants for a global view or a single tenant to audit that tenant's checks in isolation. dropdown No All Tenants
Auto Toggles automatic periodic refresh of the dashboard data. Turn it on to watch the page update during an active incident without manually refreshing; leave it off to keep the figures still while you read or compare them. toggle No off

Controls reference

Refresh

Reloads the KPI cards, Check Status Overview grid, and incident data with the current values.

When to use: After making a change elsewhere, such as creating or editing a check, or whenever the Updated timestamp looks stale.

Side effects: Read-only: it reloads data on screen and does not change any check, incident, or credential.

View all

Navigates from a panel's short preview list, such as recent incidents, to the full list on its own dedicated page.

When to use: When the panel on the dashboard shows only a few items and you need the complete, filterable list.

Side effects: Read-only: it navigates away from the dashboard without changing any data.

Check card expand/collapse

Expands a check's card to show its analytics detail inline, or collapses an expanded card back to its summary view.

When to use: When you want to inspect one check's recent trend without leaving the dashboard.

Side effects: Read-only: it only changes what is displayed on screen.

Check enabled/disabled toggle

Enables or disables monitoring for that specific check.

When to use: Before planned maintenance on the monitored service, so the check does not keep generating failures and incidents while the service is intentionally down.

Side effects: Mutating: a disabled check stops running and will not open new incidents until you re-enable it.

Verify the result

The dashboard loads successfully when the KPI cards show numeric values and the Updated timestamp is recent. The Check Status Overview grid lists one card per configured check, each showing a service-type chip, a status label, and Uptime, Last response, and Incidents figures. If the page instead shows a prompt to create your first check, no uptime checks exist yet. If the KPI cards stay blank or the Updated timestamp does not change after selecting Refresh, the dashboard failed to load current data.

Troubleshooting

  • Symptom: The Check Status Overview grid is empty and shows a prompt to create your first check. Fix: Create at least one check on the Uptime Monitoring: Checks page; the dashboard has nothing to summarize until a check exists.
  • Symptom: The Overall Uptime KPI is far lower than expected even though only a few checks are currently failing. Fix: Check the Period selector; a single long outage earlier in the window can keep dragging the overall percentage down even after the affected check recovers.
  • Symptom: A check you expect to see is missing from the grid. Fix: Reset the Environment, Service Type, and Tenant filters back to their All options; the check may simply be filtered out.
  • Symptom: The credentials expiring soon banner stays visible after you rotate the credential. Fix: Select Refresh to reload the dashboard; the banner reflects the last loaded data, not a live subscription.
  • Symptom: The Open Incidents KPI does not match what you can see in the Check Status Overview cards. Fix: Select View all to open the full incidents list, since the dashboard panel may only preview the most recent incidents.
Was this article helpful?
0 out of 0 found this helpful