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 always showing down when the servers are actually up

Dear all,

I'm pretty new with Solarwinds and just a beginner in this. Currently I am 'chosen' to administer to Solarwinds and I need to add 300++ servers of differnt functions to the Solarwind. The problem is the servers are scattered around the world and the Solarwind server is in my country. When I use a template to monitor the servers performance counter, I kept getting messages that the APM was down when it was up. I tried to configure the alerts to 10 servers and at one time, i can get 30-40++ emails. The network is not very stable btw and we are using ICMP instead of SNMP due to some security reason. Any best practise for this? And the nodes looks like Christmas lights, red green red

Find more posts tagged with

Accepted answers

FormerMember

If you don't mind having the alerts delayed a few minutes you could increase the grace period by changing the Trigger Condition section 'Do not trigger this action until condition exists for more than ' to something like 5 minutes, that way it has to exist in a down state for 5 minutes before alerting. You can do this for each alert that is active and causing issues (from the Advanced Alert Manager program).

Also Settings -> Polling Settings has the option for changing the amount of seconds to wait before marking a device as down (I think its called Node Warning Level). Try increasing this if your nodes are flapping, or increasing ICMP Timeout if the network has high latency all over.

Triggers are really flexible, but I find you really have to tweak a lot of the defaults to fit your network most of the time, and unfortunately that can take a while to get used to for a beginner.

Andy.

All comments

FormerMember

Triggers are really flexible, but I find you really have to tweak a lot of the defaults to fit your network most of the time, and unfortunately that can take a while to get used to for a beginner.

Andy.

oithim_yew

hi andy,

i had set the trigger to 8 minutes but on the polling, we had set it to 7200ms, is this right? or should i configure the polling to have a longer period? eg. 48000ms? thanks

FormerMember

7200ms is quite high already, but if your network is that bad you're always going to have trouble keeping monitoring stable regardless of the tool you use. All you can do really is tweak the settings until you get the accuracy you need.

oithim_yew

hi andy,

i got to know that the limit is 20000ms, is 7200ms is too high, what is the number that you would suggest? I tried 20000ms, the notifications seems to be stopped but since it was too high, I have revert back to 7200ms as what was set by my project team. thanks.