APM Alerts firing on nodes which do not have APMs adssigned to them

Hello all, I am having an issue with APM alert firing for nodes which have no APMs assigned to them. Has anyone had this issue and how can this be resolved?

Best regards,

Bryan

SolarWinds Orion Core 2011.1.0 SP1,

APM 4.0.2 SP3,

NPM 10.1.2 SP1,

IVIM 1.1.1

Find more posts tagged with

false_alarmsalerts

Accepted answers

All comments

FormerMember

Can you paste a screenshot of the Alert Trigger that is firing and a screenshot of the actual alert seen? Does sound odd.

bmills99

Many thanks for the assistance!

Here is the alert trigger:

This generates the following email:

Subj:

OST HDC NOC - Orion Critical Alert: ${ComponentName} on HOUPDC is ${ComponentStatus}

This application component status has changed:

8/18/2011 10:28 AM Application Name: ${ApplicationName} Application Component Name: ${ComponentName} is ${ComponentStatus}

Status Description (Info): ${StatusOrErrorDescription} Statistic/Component Value: ${StatisticData} Response Time: ${ResponseTime}

The HOUPDC is a node with no APMs assigned to it at this time...Any suggestions?

Thanks,

Bryan

FormerMember

Is this email via the Advanced Alerts 'Test' button (as it just tests the Action, not the trigger, so can vary wildly), or is it coming in naturally as part of a triggered alarm? The fact the ${} variables aren't being evaluated would suggest the type of monitor its applied against doesn't match the one that triggered which is very odd.

Might be worth raising a support ticket if this is triggering like that as part of a normal alert.

JasonFerree

Is this an actual alert that fired, or a test that you ran?

bmills99

This is an actual alert not a test...