Hi Ken (modot)
Surely if you have a dependency setup this will mean that the only time you get alerts that are NOT network related will be things that the GPS Tech need to resolve? The Dependency you have between the Switch and the GPS will suppress any alerts for the GPS if the switch is down.
Hi there modot
Have you tried adding the dependency yourself?
Go to Settings and then Manage Dependencies (http://<Orion server>/Orion/Admin/DependenciesView.aspx) and click the button.
The parent will be your switch, the child your GPS unit.
This will, when the switch is uncontactable (either its link is down or it is), suppress any alerts for the GPS unit, which will go into an unknown state.
I am well aware of how dependencies work. I know that you can suppress the child alert when the parent is down. However, that is not what I am wanting to do. The GPS tech also gets other alerts that the GPS is down from other systems. However, our system is the only one that can tell him if it's a GPS problem or a network problem. That is why I want to create a custom alert for him that tells him that the parent is either up or down so he can be certain of what action he needs to take on his end.
Only trying to help, maybe you should have been clearer, first time around then
I think you need to look at your alert then. Get it so that only the parent device can raise the alert for the GPS unit, and no other devices.
As your description is a little "high level", if we could see what alert you are using (trigger conditions - screenshot of triggers or the SQL/SWQL export) and some examples of when it doesn't work, then it might give us a little more to go on (help you with).
Perhaps you could leverage groups and do this (note the 'group member root cause'...and also note that this solution is a group solution rather than a dependency solution...also note step 6, and lastly this would require a group to be defined and configured with status rollup set to worst case):
This article lists the steps for creating an alert to trigger when a member of a group is down.
- NPM 11.5 and later
1. Log into the Orion Web Console.
2. Click Settings > All Settings > Manage Alerts.
3. Locate the out of the box alert "Group is down" & Click Duplicate and Edit.
4. Give the alert a name and complete the required details.
6. Under the Trigger Actions tab, edit the Send an Email option:
a. Click Insert Variable.
b. Find and Select the variable "Group Member Root Cause".
This variable identifies the node that caused the group to have a down status.
7. Click Save Changes and test accordingly.