Applications Systems

Create an alert for WPM when a transaction is in Unknown status

This article describes how to configure a SolarWinds Platform alert that notifies you when a WPM transaction remains in Unknown status for a configured period of time. This is useful for detecting when a playback location or transaction stops returning results (for example, after an issue on an APE or WPM player), even if the transaction is not explicitly Down.

First published date

4/14/2026 11:19 PM

Last published date

4/14/2026 11:19 PM

Overview

By default, administrators often configure alerts only when a WPM transaction is Down. However, in some situations a transaction can remain in Unknown status, such as when:

  • The transaction has not been replayed for some time.

  • The playback location has stale or interrupted communication with Orion, but not a clean failure.

  • There is a post‑upgrade or HA failover state issue that prevents new results from being recorded.

To detect and react to this condition, you can create a SolarWinds Platform alert that triggers when a WPM transaction status is Unknown for longer than a defined period (for example, more than 10 minutes).

Product section

Web Performance Monitor

Resolution

Follow the steps below to create an alert that triggers when a WPM transaction remains in Unknown status.

1. Create a new alert

  1. Log in to the SolarWinds web console.

  2. Navigate to Alerts & Activity > Manage Alerts.

  3. Click Add Alert.

On the Properties tab:

  1. Enter a name, for example:
    Name: WPM – Transaction in Unknown Status

  2. (Optional) Add a short description, such as:
    This alert triggers when a WPM transaction remains in Unknown status beyond its expected replay interval.

  3. In I want to alert on, select Transaction (WPM) (or WPM Transaction, depending on your version).

Click Next.

 

2. Define the trigger condition for Unknown status

On the Trigger Conditions tab:

  1. Ensure Trigger alert when is set to All child conditions must be satisfied (AND).

  2. Click Add Single Condition (Simple).

  3. Configure the condition:

    • Field: Status

    • Operator: is equal to

    • Value: Unknown

  4. Click More options (if available) and configure the duration:

    • Condition must exist for more than: 10 minutes

Recommendation:
Use a value that is longer than your playback interval. For a 5‑minute WPM transaction interval, 10 minutes ensures the alert only fires if at least two scheduled replays have failed to produce a result.

  1. (Optional) Limit the scope to specific locations (players), for example:

    • Add a second condition such as:

      • Field: Location or Playback Location

      • Operator: is equal to

      • Value: APE02 (or your specific location name)

Click Next.

 

3. Configure the reset condition

On the Reset Conditions tab:

  1. Select Reset this alert when.

  2. Add a condition:

    • Field: Status

    • Operator: is not equal to

    • Value: Unknown

This resets the alert when the transaction returns to a known state such as Up, Warning, Critical, or Down.

Click Next.

 

4. Add notification actions

On the Trigger Actions tab:

  1. Click Add Action and choose Send an Email/Page (or your preferred notification type).

  2. Configure recipients (for example, a WPM or NOC distribution list).

  3. Click Next and configure any Reset Actions as needed (for example, send a “resolved” email when the transaction leaves Unknown status).

  4. Review the summary and click Submit to save the alert.