Network Management

Display wireless access point name in alert email actions in SolarWinds Observability Self-Hosted

First published date

7/7/2026 6:10 PM

Last published date

7/7/2026 6:10 PM

Overview

In this scenario, an alert for a wireless access point (AP) going down was already triggering correctly and sending email notifications, but the email only showed the wireless controller or firewall node name. The customer needed the email body to also display the specific AP name so that recipients could immediately see which AP was affected.


Product section

Network Performance Monitor

Cause

In SolarWinds Observability Self-Hosted, a wireless AP alert object exposes its display name through the Name property, not the Caption property.

The email action was using this variable:

`$${N=SwisEntity;M=Caption}$$

Because wireless AP entities do not populate the Caption property, that token was not resolved and was printed literally in the email instead of showing the AP name.

Resolution

To have the wireless AP name appear in alert email notifications, use the Name property for the alert entity in the email body.

  1. Open the alert that is monitoring your wireless access points.

  2. Confirm that the alert trigger is scoped to the appropriate wireless access point entity type (for example, the Thin AP or wireless AP object, not just the controller node).

  3. Edit the alert action that sends the email notification.

  4. In the email message body, replace any use of the Caption-based token (for example, $${N=SwisEntity;M=Caption}$$) with the Name-based token:

     AP Name: ${N=SwisEntity;M=Name}
     Parent Node: ${NodeName}

    This uses the wireless AP entity’s Name property for the AP name, and the parent node’s NodeName for the controller or firewall name.

  5. Save the alert.

  6. Test the alert:

    • Either wait for the next natural trigger, or

    • Manually trigger a test on one known AP.

  7. Verify the resulting email:

    • The AP section should now show the specific AP name (for example, AP Name: YOWGNSAP002-IDF2) and the parent node name (for example, Parent Node: YOWGNSFW001).

The issue should be resolved after switching to the Name-based token: Resolved with $${N=SwisEntity;M=Name}$$.