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

${statusorerrordescription} not returning a value with APM4.2

We've been using APM for a while, and have a large number of scripted alerts set up that return the information about what failed using the ${statusorerrordescription} variable with no problems. Since upgrading to APM4.2 the scripts still run, and we can see the information on the UI, but the text is no longer being passed back in the variable. We only have one value in the script, do the scripts have to be changed to work with the new multi-value functionality?

Find more posts tagged with

Accepted answers

aLTeReGo

${StatusOrErrorDescription} doesn't appear to return anything for script monitors. If this behavior is different from the previous version I would recommend opening a case with support and logging the issue. In the meantime you can use the ${ComponentStatus} and ${ComponentMessage} variables to pass the component information in your alerts.

All comments

aLTeReGo

We're tracking this internally as FB84118

kronork

Thanks, changing the variable used in the alerts has solved the problem with getting information back.

Quick Links

All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of