Alerting: Profiles

Updated

Alerting: Profiles

Overview

Use this page to review and manage alert profiles across Monitoring, Testing, and Uptime scopes. An alert profile is a reusable rule that watches a specific data type for a severity condition and, when that condition is met, fires a notification through a configured trigger such as a webhook channel. Rather than configuring alerting separately on every check or test, you define the rule once here and apply it to the scope it belongs to.

Before a profile is useful, the notification channel it uses as a trigger must already exist, and the checks, tests, or monitoring jobs it is meant to watch must be configured in their own area of the platform. Once a profile is active, Uptime checks consume it automatically: every enabled check fires every Uptime-scoped profile by default unless you explicitly link only specific checks to it, which narrows where that profile fires.

From this page you can filter profiles by scope, read each profile's severity, trigger channel, status, linked-check count, and last-triggered history, open a profile to edit or view it, assign an Uptime-scoped profile to specific checks, or delete a profile you no longer need.

Key concepts

  • Alert profile - A reusable rule that watches a data type for a severity condition and fires a notification through a trigger when the condition is met. (related: Alerting: Triggers)
  • Scope - The platform area (Monitoring, Testing, or Uptime) an alert profile belongs to; it determines which checks or tests can use the profile.
  • Linked checks - The count of Uptime checks that explicitly include this profile in their alerting list. A count of 0 means the profile fires on every enabled Uptime check by default rather than indicating a problem. (related: Uptime Monitoring: Checks)
  • Trigger - The notification channel, such as a webhook, that delivers the alert when a profile's condition fires. (related: Alerting: Triggers)
  • Data type - The category of data a profile monitors, for example UX Metrics; the available data types depend on the profile's scope.

When to use it

  • You want to see every alert profile configured across Monitoring, Testing, and Uptime scopes in one place.
  • You need to check which notification channel a profile uses before troubleshooting a missed or unexpected alert.
  • You're setting up a new Uptime check and need to confirm whether an existing profile already fires on it by default or needs to be explicitly assigned.
  • You want to filter the list by scope before editing or reviewing only Monitoring, Testing, or Uptime profiles.
  • You need to disable, edit, or delete a profile that no longer matches a monitoring need.

Before you begin

  • The notification channel a profile will use as its trigger (for example a webhook) must already be configured under Configuration: Notification Accounts.
  • Your account role must hold at least one alerting scope (Monitoring, Testing, or Uptime); a role with no scope sees the table rendered empty.
  • For Uptime-scoped profiles you intend to link explicitly, the target checks should already exist under Uptime Monitoring: Checks.

Common workflows

Confirm whether a profile fires on all Uptime checks or only specific ones

Persona: Load-test operator or admin managing Uptime alerting

  1. Select the Uptime tab in the scope filter row.
    • Expect: The table reloads to show only Uptime-scoped profiles, and the Uptime button switches to the filled active style.
  2. Read the LINKED CHECKS chip on the profile you're reviewing.
    • Expect: A chip reading '0: fires on all by default' confirms no checks are explicitly linked, so the profile evaluates every enabled Uptime check.
  3. Select Assign to Uptime checks on that profile's row.
    • Expect: A modal opens listing Uptime checks you can select to link to this profile explicitly.

Verify: After saving your selection, the LINKED CHECKS chip updates from 0 to the number of checks you linked, confirming the profile now fires only on those checks.

Investigate why an expected alert never fired

Persona: Load-test operator troubleshooting a missing notification

  1. Locate the profile by name in the table, for example Vega evening logoff wave, optionally filtering by scope first.
    • Expect: The matching row appears, showing its Severity, Trigger, Status, and Last Triggered values.
  2. Check the STATUS column for that row.
    • Expect: If it reads anything other than Active, the profile is not currently evaluating its condition.
  3. Check the LAST TRIGGERED column.
    • Expect: A value of Never, or an old date, confirms the condition hasn't been met recently.

Verify: You've determined whether the profile is inactive, has never met its condition, or points to a misconfigured trigger channel, and can open it to correct the issue.

Steps

Step 1

Open Profiles under the Alerting section.

Expected result: The Alert Profiles page loads with the All scope tab active, listing every configured alert profile in a single table alongside a notice about an expiring credential and a banner explaining how the Linked Checks count works.

This is the starting point for reviewing or managing any alert profile across scopes.

  • The All tab is active by default, showing profiles from every scope.
  • A dismissible banner explains that a 0 LINKED CHECKS chip means the profile fires on all Uptime checks by default.
  • A separate banner flags an expiring credential, unrelated to the alert profile configuration itself. Alerting: Profiles - step 1

Tabs on this page

  • All - Shows every alert profile regardless of scope. This is the default view when the page opens.
    • Full column set: Name, Scope, Data Type, Severity, Trigger, Status, Linked Checks, Last Triggered, Count.
  • Monitoring - Filters the table to profiles scoped to End-to-End Monitoring checks.
    • Same columns as All, with every row's Scope badge reading Monitoring.
  • Testing - Filters the table to profiles scoped to Load or API Testing.
    • Same columns as All, with every row's Scope badge reading Testing.
  • Uptime - Filters the table to profiles scoped to Uptime Monitoring checks; switch here when you need to review or change which checks a profile is linked to.
    • Same columns as All; LINKED CHECKS and the Assign to Uptime checks control are only meaningful in this scope.

Column reference

Column What it shows How to read it
NAME Identifies the alert profile; the line beneath the name gives a short description of the condition it watches. Click the name to open the profile for editing, or for viewing only if your role lacks write access to that scope.
SCOPE Shows which platform area the profile applies to: Monitoring, Testing, or Uptime. This determines which checks or tests can reference the profile. Match this value against the scope tab you're filtering on; a profile only appears under its own scope tab or under All.
DATA TYPE Names the category of data the profile evaluates. The set of data types available depends on the profile's scope. Use this to confirm the profile is watching the kind of data you expect (for example end-to-end monitoring metrics rather than uptime response data).
SEVERITY Indicates how urgently to treat the condition when it fires. Use this alongside Trigger to judge how a firing event should be routed and how quickly it needs attention.
TRIGGER Names the notification channel and delivery method that sends the alert when the profile fires. Shows the destination and delivery method configured for this profile; verify this channel is still valid if an expected alert never arrived.
STATUS Shows whether the profile is currently enabled and evaluating its condition. A green dot with Active means the profile is live and will fire when its condition is met.
LINKED CHECKS Counts how many Uptime checks explicitly include this profile in their alerting list. Read 0 as default-safe, not broken: it means the profile fires on every enabled Uptime check. The chip increases once you explicitly link specific checks to the profile.
LAST TRIGGERED Shows the most recent time this profile's condition fired and sent a notification. Never means the profile has not fired since it was created; a date tells you when it last alerted.
COUNT Shows the total number of times this profile has fired. Rising counts indicate the condition is being met repeatedly; read alongside Last Triggered to judge how active a profile is.

Controls reference

Create Profile

Opens a form to define a new alert profile: its scope, data type, severity, and trigger.

When to use: Use it when no existing profile covers a condition you need to monitor.

Side effects: Read-only until you save the new profile in the form that opens; no profile is created by clicking alone.

Dismiss action error

Closes the inline error message shown after a failed attempt to open or delete a profile.

When to use: Use it once you've read the error, such as a failed open or delete.

Side effects: Read-only: hides the message without retrying the action or changing any data.

Close (Credentials expiring banner)

Dismisses the notice about a notification credential nearing expiration.

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

Side effects: Read-only: hides the banner only; it does not reissue or extend the credential itself.

Close (Linked Checks info banner)

Dismisses the banner explaining how the Linked Checks count and default-fire behavior work.

When to use: Use it once you understand that a 0 count means the profile fires on all Uptime checks by default.

Side effects: Read-only: hides the banner only.

Navigates to the Uptime check configuration where you can add this profile to a specific check's alerting list.

When to use: Use it when you want a profile to fire only on certain checks instead of every enabled check.

Side effects: Read-only navigation; no change happens on this page.

Opens the selected profile in the editor, or in read-only view if your role lacks write access to that scope.

When to use: Use it to inspect or change a profile's scope, data type, severity, or trigger.

Side effects: Read-only until you save changes inside the opened profile.

Assign to Uptime checks

Opens a modal where you select specific Uptime checks to explicitly link to this profile.

When to use: Use it when you want the profile to fire only on selected checks rather than on every enabled check by default.

Side effects: Mutating: adds this profile to each selected check's alerting list, which updates the LINKED CHECKS count on this page. Only available for Uptime-scoped profiles.

Edit icon

Opens the profile editor, the same destination as clicking the profile name.

When to use: Use it as a shortcut from the row's action icons rather than clicking the name.

Side effects: Read-only until you save changes inside the opened profile.

View icon

Opens the profile in read-only mode.

When to use: Appears in place of Edit when your role only has view access to that profile's scope.

Side effects: Read-only: no changes can be made from this view.

Delete

Permanently removes the alert profile.

When to use: Use it when a profile is no longer needed and should stop firing.

Side effects: Mutating and destructive: the profile stops evaluating immediately, and any Uptime checks that had it explicitly linked lose that link.

Verify the result

The Alert Profiles table lists every profile relevant to the selected scope tab, with each row showing its Scope, Data Type, Severity, Trigger, Status, Linked Checks count, Last Triggered date, and total Count. Switching scope tabs changes which profiles appear without altering any profile's settings. If a profile you expect to see is missing, confirm you haven't filtered to the wrong scope tab and that your role holds that scope. If an edit or delete silently fails, check for an inline error banner near the top of the table naming the profile and the reason.

Troubleshooting

  • Symptom: A profile's LINKED CHECKS chip shows 0 and you expected it to apply only to certain checks. Fix: A 0 means no explicit links exist yet, so the profile fires on every enabled Uptime check by default; use Assign to Uptime checks on that row to link it to specific checks only.
  • Symptom: You can't see Create Profile, Edit, or Delete controls for a scope you expect to manage. Fix: Your role likely doesn't hold that alerting scope; the page only offers create, edit, and delete for scopes your role has access to.
  • Symptom: The row action icons on the right edge of the table are cut off. Fix: Widen the browser window or scroll the table horizontally; the Assign, Edit or View, and Delete icons sit at the far right of each row.
  • Symptom: A profile never appears to fire even though its condition should have been met. Fix: Confirm the STATUS column reads Active and that the TRIGGER channel is still valid; also check whether the credential behind that channel is expiring, as flagged in the banner at the top of the page.
  • Symptom: Clicking a profile name opens it read-only instead of letting you edit it. Fix: Your role has view-only access to that scope; editing requires a role with write permission for the profile's scope.
Was this article helpful?
0 out of 0 found this helpful