Are Groups and Dependencies used with Basic alerts? My suspicion is that the answer is no, since dependencies are defined in the database and Basic alerts do not query the Orion database as part of their functionality.
Anyone? Thanks.
It looks like it can be done if you use the alert suppression tab in basic alerts manager when configuring the alert. You can suppress the alert for node b if node a is up... but that doesn't give you as much functionality as the advanced alert manager and would be a pain to configure for all the dependent devices. Is there a reason that you would not want to use the advanced alerts?
I use both Basic and Advanced. That is not the reason for my question. I simply want to know whether dependencies have any impact on the functionality of Basic alerts or whether they only have meaning with Advanced alerts.
Basic and advanced will be able to take advantage of your dependencies setup without a problem. The reason for that is dependencies don't really have anything to do with alert suppression, they affect how status is calculated. When a parent is down, instead of marking the child as down, it will be marked as unreachable.
How does this affect your alerts? If you have an alert set up to trigger when status is down(in basic or advanced alerts), because the node is never marked as down, the alert won't trigger. However, if you set up your alerts to trigger when your status is "not up", then it would trigger, because your status is marked as unreachable, which matches "not up".
Does that help clarify things? Or have I made it worse?
Thanks,
Casey
I understand everything you said but:
"Basic advanced will be able to take advantage of your dependencies setup without a problem".
What do you mean by basic advanced"?
That's what I get for writing up stuff on Friday afternoon. It's actually "basic *and* advanced". I've edited the initial post as well.
No problem Casey. Your explanation actually brings to mind another minor question. I know that if a dependency exists in the Orion database for an object, NPM will check the status of the parent before setting the status of the child. If the parent is a single device, is that device actually pinged again, ordoes NPM just use the current status listed in the database as of the last ping? What if the parent is a group?
Hi,
Instead of saying NPM, I'll say "Orion Platform" products since all have the same behavior.
A dependency is checked when a node (interface, volume, application, ...) is detected as being Down. It does not actively ping the parent as this would potentially lead to a lot of work for a set of 1000 great great grandchildren of a down parent. It uses the status from the database.
Look at my posts at these locations and see if I give more clarity as to how this works.
Sorry, but there is a lot of information out there from all the questions that have been asked. Let me know if I can clarify anything.
Thanks
