Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Informative Alert examples

Hello,

I'm looking at improving the information sent out in email alerts.

My default email text for "Alert me when an Application goes Down" is fairly limited...

"NetPerMon Event Log: Application ${Name} on Node ${NodeName} is ${Availability}

CMDB Location: ${Node.CMDB_Location}
CMDB Description: ${Node.CMDB_Description}"

${Node.CMDB_Location} and ${Node.CMDB_Description} are Custom Properties on the Node.

How do people use the ${ComponentsWithProblems} and ${ComponentsWithStatus} variables? The APM documentation says that it returns comma delimited lists, but it isn't clear how to turn that into a useful email message.

Also, can I get to any status information that the monitor has access to when it fails? In the web interface I saw an error with text similar to "Oracle error: 1234", but is that exposed as a variable for email alerts?

Would anyone share their example "Application Down" or "Application Critical" emails?

Thanks for any help.

~sm

Find more posts tagged with

advanced_alerts

apm

variable

Accepted answers

qle

How do people use the ${ComponentsWithProblems} and ${ComponentsWithStatus} variables? The APM documentation says that it returns comma delimited lists, but it isn't clear how to turn that into a useful email message.

${ComponentsWithProblems} as you've indicated, outputs a comma delimited list of components that play a part in an application not being up. Listed in parentheses next to each component is its status (e.g. Unknown, Down, etc.)

${ComponentsWithStatus} is similar except that all components are listed, regardless of status.

Also, can I get to any status information that the monitor has access to when it fails? In the web interface I saw an error with text similar to "Oracle error: 1234", but is that exposed as a variable for email alerts?

As Jiri has indicated already, if you want to expose a component's error status in the e-mail alert, you'll need to set the Type of Property to Monitor to APM: Component. Keep in mind that variables for both applications and components are available with APM: Component whereas with APM: Application, only the application variables are available to you.

All comments

jiri.tomek

Hello Simon,
message displayed in UI by failing component is available in variable ${StatusOrErrorDescription}. This variable is available only for APM:Component, not for whole application. You will have to create alert on APM:Component and then you can include this variable in alert message.

SimonMorris

Hi Jiri,

Thanks for the reply.

We aren't alerting for components going into critical or warning state by email at the moment, but we are getting Application alerts for an individual component.

Does it make more sense to alert on the individual components... If I get an email for the Application going into warning state it would be better to have access to the ${StatusOrErrorDescription} variable.

Thanks

~sm

qle

How do people use the ${ComponentsWithProblems} and ${ComponentsWithStatus} variables? The APM documentation says that it returns comma delimited lists, but it isn't clear how to turn that into a useful email message.

${ComponentsWithStatus} is similar except that all components are listed, regardless of status.

Also, can I get to any status information that the monitor has access to when it fails? In the web interface I saw an error with text similar to "Oracle error: 1234", but is that exposed as a variable for email alerts?