Node Properties: Alerting Thresholds, but Hardcoded Values in Advanced Alert Manager

This is a new install of NPM, and I have a question about the default alerts.

Under each node's properties, there is a section for "Alerting Thresholds":

1. Thresholds.PNG

However, when I look at advanced alert manager, it has a value hardcoded (This is from the default alert "High Response Time Monitoring"):

2. Trigger Condition.PNG

To further confuse things, the Trigger Action email uses a variable:

3. EmailPage Action.PNG

I've verified that the 200ms is what's triggering the alert. The default alert tells me that the response time exceeded 1000 (or whatever the global threshold is), but I had the email also include the average response time, and it is just over 200ms for these sites in China (which is to be expected). That is, the modified email from the advanced alert sends me:

"Response time for node <chinafqdn> has exceeded 1000.

Average Response Time: 229 ms"

How do I use the per-node thresholds for alerting?

Find more posts tagged with

thresholds

node_specific_threshold

Alerts

Accepted answers

borgan

I must disagree with mharvey. I tested the following scenario successfully as it relates to percent memory utilization for nodes. I disabled any advanced alert dealing with memory utilization so as to remove that variable in the test. I then edited two specific nodes to enable the "Override Orion General Thresholds" feature. I then manually entered a static value for the Warning and Critical thresholds that I knew would cause the alert to trigger.. I then created a test alert that applies only to the two test nodes as shown in the screenshot. When I enabled this alert, I immediately received an alert. 12-8-2014 11-18-17 AM.jpg

All comments

mharvey

I don't think there is a way to do that at the moment. The per node threshold is merely for the website on when it shows the value in yellow or red, but does not carry over to the alerting.

borgan

goodzhere

This is a way to get around this. In Advanced Alert Manager, under the Trigger condition tab, you can add lines to ignore specific nodes. Add simple condition Node Details>Node Name is not equal to (specific node). Add this for each node you do not want this applied to. Then you can create a copy of that alert and make an alert for the specific nodes with the higher response time, by adding an "if any" above the specific nodes. Is this what you are looking for?

mharvey

Ah ok, so they did start incorporating these into the alerting as well as the website. Thanks for the new information borgan.

goodzhere

It has always been there at least since NPM 9

borgan

Even a blind squirrel......

mharvey

As far back as I've used the product I had never seen that capability in the alerts. I know the threshold option has always been there in the web, but not a connecting alert to that threshold value for Node statistics.

fdamstra

Thank you for this! It was the "* threshold is reached" criteria I was missing. They should really update it to ship with alerts based off these instead of the hardcoded 200ms.

aLTeReGo

NPM 12.5 includes support node thresholds affecting the status of the node, allow you to alert on a node going into a warning or critical state. For more information, see the following post.

Orion Platform 2019.2 - Enhanced Node Status