Uptime Monitoring: My dashboard

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.

Uptime Monitoring > My dashboard opens your personal default dashboard when you have one, else the appliance default dashboard, else the fleet page of every check that this article describes. 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's run fails and the check's Failure Mode says so, the check 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 status grid by environment, service type, and tenant, choose the time period, 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)
  • check status - The verdict of the check's latest run: Healthy, Degraded (the run passed but took longer than the check's own Warning Threshold, or carried a warning, for example vulnerable packages on a repository scan, or the SSL certificate expires within the warning days, 30 by default) or Unhealthy (the run failed). The Healthy, Degraded and Unhealthy KPI cards count enabled checks only. (related: Uptime Monitoring: Checks)
  • incident - A period during which a check is failing. It opens only on a failed run, and only once the check's Failure Mode says so: Immediate (the default: the first failure), after a number of failures in a row (3 by default), or a number of failures within a time window. A Degraded check never opens an incident, and neither does a manual run. It closes automatically on the first passing run (a Degraded run passes too) or after the number of passing runs the check is set to require; it also closes when the check is deleted, or when you resolve it by hand. (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. Every check uses one, enabled or disabled, and deleting a check frees it. 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 Uptime Monitoring 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 Uptime Monitoring > My dashboard. If it opens a dashboard of your own, select Uptime Monitoring > Dashboards and then Fleet overview.
    • 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 enabled checks are currently failing and how many incidents are open.
  3. Select the Refreshbutton 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 and Open Incidents counts that match the 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 Check Status Overview grid shows 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 Check Status Overview grid lists only the checks that match both filters, confirming the filters applied.

Steps

Step 1

Open the Uptime Monitoring Dashboard with Uptime Monitoring > My dashboard or, when that opens a dashboard of your own, Uptime Monitoring > Dashboards and then Fleet overview.

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, and the Recent Incidents table.

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 expire within 30 days, with a View all link that opens Uptime Monitoring > Reminders.
  • A license usage bar shows how many of your licensed endpoints are currently in use.
  • Each check card's colored top bar flags its status: green for Healthy, yellow for Degraded, red for Unhealthy, blue for Maintenance and grey for Dep. Down. A disabled check's card is grey with a dashed border. Uptime Monitoring: My dashboard - step 1

Field reference

Field Purpose Format / Validation Required Default
Period selector Sets the time window the uptime figures (Overall Uptime and each card's uptime percentage) are calculated over, counted back from now, from Last 5 Minutes to Last 90 Days. 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. Open incidents are counted whatever the period. dropdown No Last 24 Hours
Environment filter Restricts the Check Status Overview grid 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 Check Status Overview grid 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 Check Status Overview grid to checks belonging to one tenant in a multi-tenant deployment. The list shows the tenant ids set on your checks. 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 at the interval you pick next to it: 5s, 30s, 1m or 5m (1m by default). 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. The Updated timestamp keeps counting either way. checkbox No off

Controls reference

Refresh

Reloads the KPI cards, Check Status Overview grid, and incident data with the current values. The credentials banner loads with the page and is not reloaded.

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

On the credentials banner, opens Uptime Monitoring > Reminders with every credential that is close to expiring. Recent Incidents lists up to 10 open incidents; the full list is on the Uptime Monitoring: Incidents page.

When to use: When the banner shows credentials expiring soon and you need the complete list.

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

Analyze / Hide Analytics

Analyze on a check card opens one Analytics panel for that check below all the check cards. The panel shows the check's Uptime, Total Checks (the runs in the period), Avg Response and P95 Response figures, the Min, Avg, P95 and Max response times, a passed and failed bar when runs failed, its own period buttons, and Ask AI about this check where AI analysis is available to you. Close it with Hide Analytics on the card or the X in the panel's header.

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: the page reloads at once. A disabled check stops running and will not open new incidents until you re-enable it; its card turns grey with a dashed border and a Disabled label. A disabled check still uses its license seat.

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.

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, and select a highlighted KPI card again to clear its quick filter; the check may simply be filtered out.
  • Symptom: The credentials expiring soon banner stays visible after you rotate the credential. Fix: Reload the page in your browser; the banner loads with the page, and Refresh does not reload it.
  • Symptom: The Open Incidents KPI does not match the incident counts on the Check Status Overview cards. Fix: Open Uptime Monitoring: Incidents for the full list of open incidents and the checks they belong to.
Was this article helpful?
0 out of 0 found this helpful