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

APM 2.5 Application Alerting Issues

Hello all,

I have come against a couple of problems that I am hoping to get help with!

First, I really like the new APM/NPM updates. They are really making monitoring a lot easier. However I am having issues with setting up alerts for Applications and Compnents.

Let me first explain what I am trying to accomplish. I want to monitor applications as a service. Exchange Services, Domain Services, Web Services, etc.

So if any of the components fails that support the service as a whole I will get an alert for that component, no matter if it's a process that fails or a TCP Port, etc. I want to add a contingency that if the Node is down, I won't spam everyone with 50 component alerts. I have Basic alerts monitoring Node uptime.

2 problems that I have been coming up with are this. If one of our admins reboots a server for routine maintenance everyone gets 50-100 alerts, one for each server in that application and for each component monitored on each server.

The other problem is if I add a new Application Monitor with no active alerting yet on servers that currently are not added to any other APM apps all of the active alerts throw Reset alerts?

I may be over explaining and there is most likely a simple explanation so I will digress for now and look forward to any help that you can provide

Thanks in advance,

Josh

Find more posts tagged with

Accepted answers

All comments

borgan

A couple of quick suggestions that might help. If you are rebooting a server for scheduled maintenance, you may want to either disable all appropriate alerts in System Manager. or at least disable the alert actions to prevent all these alerts from firing.

If the maintenance is scheduled at a set time, you could set the alerts and/or alert actions to be active only during the other hours of the day. That would also keep them from firing during the hours in which maintenance might take place.

One other option would be to suppress the application and/or component alerts if the node to which they are attached is "not up". Therefore, if the node is in any other state other than "up", the alerts will not fire.

Good luck. Let us know if you need any help with these suggestions.

jkealiher

Thanks for the feedback, I will look into the supression options.

This is not an answer for all of the questions that I have listed in this post. The real problem that I have with the apm monitors.

Why are they spamming all active alerts if I add a new app template? Why are alerts for other applications firing for servers that don't have those active components?

Thanks for the quick feedback, but there is more to this question