Uptime Monitoring: Checks

Overview

Use this page to review uptime check health and manage check configurations. An uptime check is a configured probe, such as DNS, HTTP, ICMP, TCP, or Web, that LoadGen runs against one endpoint on a repeating interval to confirm it is reachable and responding. This page gives you one list instead of checking each endpoint by hand.

Checks you create or import here feed the uptime dashboards in Uptime Monitoring: Dashboards and Uptime Monitoring: My dashboard, and a check that keeps failing generates the records tracked in Uptime Monitoring: Incidents. A check against an authenticated endpoint needs a credential from Configuration: Credential Profiles first; this page's banner warns you when one of those credentials is close to expiring.

This page itself lets you filter checks by Environment, Service Type, Group, or tag, see each check's status, type, endpoint, and interval, and act on one: trigger it now, edit or duplicate its configuration, enable or disable it, or delete it. You can add checks individually with New Check or in bulk with Import.

Key concepts

• uptime check - A configured probe that LoadGen runs on a repeating interval against one endpoint, for example DNS, HTTP, ICMP, TCP, or Web, to confirm it is reachable and responding correctly. (related: Uptime Monitoring: Incidents)
• tag - A free-form label attached to a check, for example Production or TCP, that you can toggle on in the tag row to narrow the list alongside the Search, Environment, Service Type, and Group filters.
• credential profile - A stored set of authentication details, such as a bearer token, that a check can use to reach a protected endpoint. (related: Configuration: Credential Profiles)
• interval - How often LoadGen re-runs a check automatically, shown per row, for example 5m for every 5 minutes.

When to use it

• You want a single view of which endpoints are currently healthy versus failing.
• You need to find the reason a specific check is failing before escalating it.
• You're onboarding a new endpoint and need to create or import a check for it.
• You need to pause a check during planned maintenance or remove one that's no longer needed.
• A credential used by a check is expiring and you need to find which check is affected.

Before you begin

• Know the endpoint (hostname, IP address and port, or URL) you want to monitor.
• If the check will probe an authenticated endpoint, create the credential it needs first in Configuration: Credential Profiles.
• Decide which Environment, Service Type, Group, and tags to use so the check filters consistently with the rest of your list.
• Have a JSON export ready if you plan to add checks in bulk with Import rather than one at a time.

Common workflows

Find and resolve a failing check

Persona: Load-test operator or admin

1. Click the Issues summary card.
   • Expect: The table filters to only checks currently Unhealthy or Degraded.
2. Read the status-detail line beneath the failing check's name.
   • Expect: The line shows why the probe is failing, for example a connection failure reason.
3. Click the row's Trigger Now icon after addressing the cause.
   • Expect: The check runs immediately; if the run is accepted asynchronously, a notice confirms it is in progress and the row doesn't change until the run finishes.

Verify: The check's Status badge changes to Healthy and the Issues count on the summary cards drops by one.

Create a new uptime check

Persona: Admin

1. Click New Check in the page header.
   • Expect: The check creation form opens.
2. Configure the endpoint, type, and interval, then save.
   • Expect: A new row appears in the list sorted alphabetically by name, and the Total Checks count increases by one.

Verify: The new check's row shows the expected Type, Endpoint, and Interval values, and it appears under the Enabled count if left enabled.

Pause a check during planned maintenance

Persona: Load-test operator

1. Use Search or the Environment, Service Type, or Group filters to locate the check.
   • Expect: The table narrows to the matching check or checks.
2. Click the row's enable/disable toggle icon.
   • Expect: The check becomes disabled and the Enabled count on the summary cards decreases by one.

Verify: The check no longer counts toward Enabled and stops running on its interval until you toggle it back on.

Steps

Step 1

Open Checks under Monitoring and Uptime.

Expected result: The Uptime Checks list loads with 8 total checks, summary cards for Total Checks, Healthy, Issues, and Enabled, a Filters panel with Search, Environment, Service Type, and Group, a row of tag chips, and a Credentials expiring banner.

This is the starting view for reviewing which endpoints are currently healthy and which need attention.

• Total Checks, Healthy, Issues, and Enabled are clickable cards that filter the table below.
• The Credentials expiring banner flags a token nearing expiry and points to Configuration → Credential Profiles to reissue it.
• The tag row (Demo, DNS, HTTP, ICMP, LoadGen, Network, Production, SSH, TCP, TLS, Web) adds filters alongside Search, Environment, Service Type, and Group.

Step 2

Click Refresh in the page header.

Expected result: The check list reloads with each check's latest status; the Credentials expiring banner is no longer shown, revealing the Refresh, Import, and New Check buttons in the header.

• Refresh re-fetches the list; it doesn't change any check's configuration.
• Import opens a flow to add checks in bulk from a JSON file; New Check opens the form to add one check.

Field reference

Controls reference

Close (banner)

Dismisses the Credentials expiring banner.

When to use: Use it once you've noted the warning or already reissued the credential.

Side effects: Read-only: hides the banner for the session; it does not reissue or renew the credential.

Filters

Shows or hides the Search, Environment, Service Type, and Group filter row.

When to use: Use it to free up screen space once your filters are set, or to reopen them.

Side effects: Read-only: toggles panel visibility only.

Total Checks (card)

Resets all active filters and shows every configured check.

When to use: Use it to return to the full list after narrowing with another card or filter.

Side effects: Read-only filter reset.

Healthy (card)

Filters the table to only checks currently in the Healthy status.

When to use: Use it to confirm which endpoints are currently fine.

Side effects: Read-only filter toggle.

Issues (card)

Filters the table to checks currently Unhealthy or Degraded.

When to use: Use it first when triaging, to see only the checks that need attention.

Side effects: Read-only filter toggle.

Enabled (card)

Filters the table to checks that are currently enabled.

When to use: Use it to confirm no check was accidentally left disabled.

Side effects: Read-only filter toggle.

Tag chip

Toggles a tag on or off as an active filter.

When to use: Use it to combine with Search, Environment, Service Type, or Group when the structured filters alone aren't specific enough.

Side effects: Read-only filter toggle.

Clear filters

Clears every active filter (search text, Environment, Service Type, Group, tags) in one click.

When to use: Use it when you've finished a filtered review and want the unfiltered list back.

Side effects: Read-only reset.

Refresh

Reloads the check list and re-fetches each check's latest status from the server.

Side effects: Read-only: re-fetches data, does not change any check's configuration.

Import

Opens a flow to add multiple checks at once from a JSON file instead of creating them one by one.

When to use: Use it when you're onboarding a batch of endpoints that already have check definitions prepared.

Side effects: Opens the import flow only; no checks are created until you upload and confirm a file inside that flow.

New Check

Opens the form to configure a single new uptime check.

When to use: Use it to monitor one additional endpoint.

Side effects: Opens the creation form only; no check exists until you save it.

Edit (row)

Opens the selected check's configuration for editing.

When to use: Use it to change a check's endpoint, interval, type, or other settings.

Side effects: Opens the edit form only; no change is saved until you submit it there.

Trigger Now (row)

When to use: Use it to re-test a check right after you believe you've fixed the underlying issue.

Side effects: Mutating: starts a new run; if the server accepts it asynchronously, a notice shows the run is in progress and the row's status doesn't update until it finishes.

Duplicate (row)

Creates a new check pre-filled with the same configuration as the selected one.

When to use: Use it to quickly add a similar check for a related endpoint instead of configuring one from scratch.

Side effects: Mutating: adds a new check to the list once saved.

Enable/disable toggle (row)

Switches the selected check between enabled and disabled.

When to use: Use it to pause a check during planned maintenance without deleting its configuration.

Side effects: Mutating: a disabled check stops running on its interval and no longer counts toward the Enabled card.

Delete (row)

Removes the selected check after you confirm in the Delete Check dialog.

When to use: Use it only for checks you no longer need.

Side effects: Mutating and permanent: the check stops monitoring its endpoint and is removed from the list.

Verify the result

You've successfully reviewed uptime check health when the Issues count on the summary cards matches the number of rows showing an Unhealthy or Degraded status badge, and each failing row's status-detail line explains the cause. After you trigger, edit, or re-enable a check, its row updates to reflect the new status and the Healthy, Issues, and Enabled counts adjust accordingly. If you just created or imported checks, confirm success by checking that the Total Checks count increased by the expected number and the new rows appear in the table. If a count doesn't match what you expect, click Refresh to re-fetch the latest status before assuming something is wrong.

Troubleshooting

• Symptom: A check still shows Unhealthy right after you click Trigger Now. Fix: The run may still be in progress; a run accepted asynchronously only starts the check, wait for it to finish and click Refresh before re-checking the status.
• Symptom: The Refresh, Import, and New Check buttons aren't visible in the page header. Fix: Dismiss the Credentials expiring banner (or any other active banner) using its Close control; it covers the header toolbar until closed.
• Symptom: A check you expect to see is missing from the list. Fix: Check the active filters, an Environment, Service Type, Group, or selected tag may be excluding it; click Clear filters or the Total Checks card to reset.
• Symptom: The Issues count doesn't match the rows you can see on screen. Fix: Scroll the table, Issues counts both Degraded and Unhealthy checks across the full list, not only the currently visible rows.
• Symptom: An authenticated check keeps failing with an auth-related reason even though the endpoint is up. Fix: Check the Credentials expiring banner and the credential's status in Configuration: Credential Profiles; an expired token causes the probe to fail independently of the endpoint.

Related articles

• Next step: Uptime Monitoring: Incidents - Checks that stay unhealthy generate the incidents tracked there
• See also: Uptime Monitoring: Dashboards - Aggregates check health into visual dashboards
• See also: Uptime Monitoring: My dashboard - Personalized view of the checks you follow
• Prerequisite: Configuration: Credential Profiles - Checks against authenticated endpoints need a credential created there
• See also: Uptime Monitoring: Maintenance - Suppresses alerts for checks during planned maintenance windows