Alerting: Profiles

Overview

Use this page to create and assign alert profiles. An alert profile is a reusable rule that pairs a condition and severity with a notification trigger, so LoadGen notifies the right channel automatically instead of someone watching dashboards. Profiles are scoped to Monitoring, Testing, or Uptime, and the scope determines which data type a profile watches and how it links to what it monitors.

A profile depends on data already produced elsewhere: End-to-End Monitoring schedules feed Monitoring-scoped profiles, load-test runs feed Testing-scoped profiles, and Uptime checks feed Uptime-scoped profiles, while the notification destination is configured separately as a trigger. An Uptime-scoped profile fires on every enabled check by default until you link it to specific checks from that check's own Alerting step.

This page lists every alert profile you can access, filterable by scope, and lets you create a new one, open an existing one to view or edit it, restrict an Uptime profile to specific checks, or delete one you no longer need.

Key concepts

• alert profile - A reusable rule that defines a condition and severity, scoped to Monitoring, Testing, or Uptime data, and points to a notification trigger that fires when the condition is met. (related: Alerting: Triggers)
• scope - The platform area an alert profile watches: Monitoring (End-to-End Monitoring data), Testing (load-test run data), or Uptime (Uptime check data). (related: Main: Monitoring and Uptime)
• trigger - The notification channel and delivery method, for example a webhook, that an alert profile sends to when its condition fires. (related: Alerting: Triggers)
• linked checks - The count of Uptime checks that explicitly list a profile in their own Alerting step. A 0 count means the profile fires on every enabled Uptime check by default, not that it is misconfigured. (related: Uptime Monitoring: Checks)

When to use it

• You need to review which alert profiles already exist across Monitoring, Testing, and Uptime before creating a new one.
• You need to create a profile that notifies a channel when a specific condition occurs, such as a slow logon, a failed test run, or a down Uptime check.
• You need to restrict a profile that currently fires on every enabled Uptime check to only a specific subset of checks.
• You need to confirm whether a profile has ever fired by checking its LAST TRIGGERED and COUNT values.
• Your role shows an empty list on this page and you need to confirm whether that is a scope permission issue rather than genuinely no profiles.
• You need to edit or delete a profile that no longer matches the condition or destination you want.

Before you begin

• Confirm your account role holds the Monitoring, Testing, or Uptime alerting module for the scope you plan to work in; a role without it shows no profiles for that scope.
• Set up the notification channel a new profile should send to as a trigger on Alerting: Triggers before creating or editing a profile that points to it.
• If you plan to restrict a profile to specific Uptime checks, identify or create those checks first on Uptime Monitoring: Checks.

Common workflows

Create an alert profile for a Testing scenario

Persona: Load-test operator

1. Select Create Profile.
   • Expect: The profile creation flow opens for choosing scope, data type, severity, and trigger.
2. Set the scope to Testing, define the condition and severity, choose a trigger, and save.
   • Expect: The new profile appears in the table under the Testing scope tab with STATUS showing Active and COUNT at 0.

Verify: Switch to the Testing scope tab and confirm the new profile is listed with the SEVERITY and TRIGGER you configured; LAST TRIGGERED shows Never until the condition first fires.

Restrict an Uptime alert profile to specific checks

Persona: Admin

1. Select the Assign to Uptime checks icon on an Uptime-scoped profile's row.
   • Expect: A modal opens listing the Uptime checks you can link to this profile.
2. Select the checks that should use this profile and save.
   • Expect: The modal closes and the profile's LINKED CHECKS chip updates from the default 0 to the number of checks you selected, turning from neutral to green.

Verify: Reopen the profile row and confirm LINKED CHECKS shows the new count instead of 0; only the checks you selected now fire this profile.

Steps

Step 1

Open the Profiles page under Alerting.

Expected result: The Alert Profiles list loads with the All scope tab active, showing the existing profiles in a table alongside an informational banner about default Uptime linking.

Starting from the full list lets you see every profile across scopes before filtering, creating, or editing one.

• The Create Profile button in the top right opens the profile-creation flow.
• The banner explains that a 0 LINKED CHECKS chip means the profile fires on all enabled Uptime checks by default.
• The scope tabs (All, Monitoring, Testing, Uptime) filter the table below to one scope at a time.

Tabs on this page

• All - Shows every alert profile you can access, regardless of scope.
  • Same columns as the scoped tabs; use this view for a full inventory across Monitoring, Testing, and Uptime.
• Monitoring - Narrows the table to profiles scoped to End-to-End Monitoring data.
  • DATA TYPE reflects Monitoring metrics such as UX Metrics; the default Uptime fire-on-all behavior described in the banner does not apply to this scope.
• Testing - Narrows the table to profiles scoped to load-test run data.
  • Same column set as All; the default Uptime fire-on-all behavior described in the banner does not apply to this scope.
• Uptime - Narrows the table to profiles scoped to Uptime checks.
  • LINKED CHECKS is meaningful here: a 0 chip means the profile fires on every enabled check by default until you assign it to specific checks.

Column reference

Controls reference

Create Profile

Opens the flow to create a new alert profile.

When to use: Use it when no existing profile covers the scope, condition, and trigger you need.

Side effects: Mutating: once you complete and save the flow, a new profile row appears in the table under its scope.

Dismiss

Closes the informational banner that explains the default Uptime linking behavior.

When to use: Use it once you understand the LINKED CHECKS behavior and want more room for the table.

Side effects: Read-only: only hides the banner, no profile data changes.

Profile name link

Opens the selected profile.

When to use: Use it to inspect or change an existing profile's scope, condition, severity, or trigger.

Side effects: Read-only by itself: opening the profile does not change data; whether you can then edit depends on your role's permissions for that scope.

Assign to Uptime checks

Opens a modal to link or unlink specific Uptime checks to this profile.

When to use: Use it when an Uptime-scoped profile should fire only on certain checks instead of every enabled check by default.

Side effects: Mutating: saving changes the profile's linked-check list, which updates the LINKED CHECKS chip count and color.

Edit

Opens the profile in an editable form.

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

Side effects: Mutating once saved: updates the profile's row values for SCOPE, DATA TYPE, SEVERITY, TRIGGER, and STATUS.

View

Opens the profile in a read-only form.

When to use: Use it when your role has read access to that scope but not edit rights, or to inspect a profile without risking a change.

Side effects: Read-only: no data changes.

Delete

Opens a confirmation dialog, then removes the profile permanently if you confirm.

When to use: Use it to remove a profile that no longer matches a condition you want to watch, for example after retiring the check or test it covered.

Side effects: Mutating and destructive: once confirmed, the profile is removed from the table and stops being evaluated; any Uptime checks that explicitly linked it no longer fire it.

Verify the result

After you create, edit, or assign an alert profile, it appears in the table with its SCOPE badge, SEVERITY, and TRIGGER matching what you configured, and STATUS showing Active with a green dot. For an Uptime-scoped profile you just restricted to specific checks, the LINKED CHECKS chip changes from the default 0 (fires on all by default) to the number of checks you selected. LAST TRIGGERED stays Never and COUNT stays 0 until the condition actually fires, at which point both update. If a profile you expect to see is missing, check the active scope tab first, then confirm your role holds the alerting module for that scope.

Troubleshooting

• Symptom: The table is empty even though you expect profiles to exist. Fix: Confirm your account role holds the Monitoring, Testing, or Uptime alerting module for the scope you are viewing; a role without that module sees no rows for it.
• Symptom: A profile's LINKED CHECKS chip shows 0 and you assumed the profile does nothing. Fix: A 0 chip means the profile fires on every enabled Uptime check by default; use Assign to Uptime checks only if you want to restrict it to specific checks.
• Symptom: You cannot find an Edit or Delete icon on a profile's row. Fix: Row actions are limited by your role's permissions for that profile's scope; a role without edit rights sees only the View icon.
• Symptom: Opening or deleting a profile fails with an error message. Fix: Read the message text, it states the reason returned by the platform rather than a generic failure; resolve the stated cause and retry.
• Symptom: LAST TRIGGERED stays Never long after you expect the alert to have fired. Fix: Confirm the TRIGGER channel is correctly configured on Alerting: Triggers and that the profile's data type and scope match the live data actually being produced.

Related articles

• Next step: Uptime Monitoring: Checks - open a check's own Alerting step to link this profile instead of letting it fire on all checks by default
• Prerequisite: Alerting: Triggers - configure the notification channel a profile's trigger sends to before creating the profile
• See also: End-to-End Monitoring: Dashboard - review the Monitoring-scoped log and metric data that Monitoring-scope alert profiles evaluate
• See also: Testing: Test Runs - review the load-test run data that Testing-scope alert profiles evaluate