Interpreting Actionable Alerts

  • Published on Feb 13, 2026
  • 2 minute(s) read
  • j
  • s
 Prev Next

Introduction

This article explains how to interpret critical Actionable Alerts from WXP Collaboration and what steps UC engineers should take when an alert is triggered.

Critical Alerts

When users receive alerts from WXP Collaboration, they must understand what they mean and what actions are required to resolve them.


As a recipient of the critical alert, I’m unclear about what it indicates, whether it truly requires action, and how to resolve the issue to stay ahead of user complaints and minimize endpoint downtime.

Solution

If you are a UC engineer and received this critical alert from the WXP Collaboration monitoring engine, you need to take some action. When you get one of these alerts, you should be able to answer the following questions at first:

  • What endpoint is down ?- Endpoint name

  • Does the alert matter? - Once you have the endpoint name, you will be able to figure this question out.

  • How to fix this issue? - Once you have the endpoint name, it becomes easy to investigate the issue.  Currently, we can 'Group By' all metrics, including call controls, meetings, trunks, etc. The 3 'Group By' options are shown in the image below:

Group By - Nothing

When we do not supply a Group By value, a single notification will be sent when the alert conditions are met. This is the default behavior of WXP Collaboration alerts. Once Actionable Alerts are enabled for your organization, you will see that your existing alerts will show ‘Nothing’ in the Group By dropdown.

The Group by Nothing page is the single notification when the alert conditions are met; in this example, we are using all call streams and sending an alert if we stop seeing any call streams for more than 5 minutes.
1)Set filter conditions for these calls, Filter and Search.
2) Define Status Trigger(s) Set and add multiple triggers for Critical, Warn, and Info.

Here’s an example of how the alert email appears:

Group By Simple

Separate notification for each Call/Endpoint when the alert trigger conditions are met. This Group By condition will send a separate notification for each call or endpoint when the alert conditions are met.

So if you have three endpoints in the alert, and the alert condition is met for two of them, you will receive two emails (one for each endpoint). When we select Endpoints, we can either set a dynamic filter as shown or select individual endpoints.
1)Trend Chart updates to show the multiple Calls/Endpoints.
2)Group by “Simple” also simplifies the status trigger by locking down the Metric Value to 0.

Here’s an example of how the alert email appears:

Group By Advanced

Separate notifications for each group when the alert trigger conditions are met. If you selected Model type, had two DX80’s in the same group, and both met the alert condition, you would receive a single email for both DX80’s. You can choose from the multiple available options for each metric.

In the example below, we have selected Model and tags. Similar to the Single group by, we will now start grouping models and tags. If multiple endpoints start raising alerts, we will only send an alert for all endpoints that raise it for each model and tag.

Here’s an example of how the alert email appears:

To know more about Tech Insights Monitoring rules, you can refer to the article: New in Tech Insights Monitoring - Intelligent Monitoring Engine

Contact Us

If you encounter any issues, create a support case or email support@wxp.hp.com.

Related articles