Dependencies and Warning State

Hi,

My Question today is kind of two fold.

I have set up dependencies for the different sites across the globe, so that we only receive on alert when all the nodes in that group goes down. So I created a root group for the country, then a sub group for the site within the country (some countries have more than 5 sites) and then another sub group containing all the nodes. Thus if the nodes for site 1 is down, then the alert will only raise an alert for that site (not the whole country), I have then in turn (before adding the sub groups into the main groups) created the dependencies, and then added the sub groups into their parents for better display. We had a site down last night, no alert was triggered since it is checking for site DOWN, this site remained in warning state for more than 5 hours. Thus no alerts raised. My Questions are as follows:

Why would the nodes and the site remain in Warning state for that long? The theory is that they should change to down after 30 seconds (my polling settings are set to that)
Does the dependency have anything to do with it, or is it that my dependency no longer works because I added them as an object into the parent group?

EXAMPLE:

Sorry can't display the node names

Please help, this is making me brain dead.

Find more posts tagged with

dependencies

group dependency alert

warning status

manual dependencies

Accepted answers

All comments

robt

"Portsmouth Nodes" would only be down if all monitored nodes within it, were down.

grapgat

I am aware of that, the issue is that they go into a warning state, and then they remain in warning for more than 5 hours, thus never goes "DOWN" when in fact they are completely off

adam.beedell

Hi There,

Why would the nodes and the site remain in Warning state for that long? The theory is that they should change to down after 30 seconds (my polling settings are set to that)

A1) The Site (the group) status will depend on the setting below - In your screenshot it looks like the default "Mixed Status." option is on, which would keep it in a "warning" state. You'd either need to switch the behaviour to "Show Worst" or change the sub-group design (use more) to get it to behave differently

A2) The node warning state will depend on the ping settings and the packet loss (assuming an NPM node, different rules for VMAN and SAM)- You could get a constant warning state with a consistent 50% packet loss (eg. load balancing issue). Doesnt sound like this is your problem, and most of the time that'd give a flapping status due to chance

Does the dependency have anything to do with it, or is it that my dependency no longer works because I added them as an object into the parent group?

A1) I dont think so - Dependencies create the "unreachable" status and not a lot else, shouldn't be involved here