This content has been marked as final. Show 5 replies
I would rather not blackout all targets on a host EXCEPT the agent as this gets old with our number of hosts and dbs, does anyone know which rule is responsible for the mails and how they could be suppressed temporarily in an efficient way?
The rule name - Database Availability and Critical States,Target Availability Event Rule - is part of the email notification. You can find the rule in the "Incident Rules - All Enterprise Rules" page, which is accessible through Setup > Incidents > Incident Rules.
You can suppress mail notification by editing the rule to remove the Email To and/or Email Cc value in the Notifications section of the Add Actions page (2nd step in The Edit rule set process).
Thanks for your feedback.
From the rule for Database Availability, I assumed that a mail gets sent only in the event of the database being down.
The rule itself checks for target (=database) availability, and when editing, the only checkbox marked is the "Down" checkbox. The "Agent unreachable" is not checked.
From your feedback, I understand that this "down" rule includes agent down states. Not sending this event is a good idea in my opinion, as an agent down notification can also be sent by the host, and reducing mail flooding is always a good idea. Editing the notification rule is only a temporary workaround, as this will prevent me from getting notice when the database goes down (if I understand correctly)?
I think Jay was referring to selecting availability events by severity. So in the rule create/edit "Select Events" step you can do the following:
1. select (event) Type= Target Availability
2. Leave the radio button in the sub-section at "All events of type Target Availability"
3. select the check box next to "Severity" right below the Type field
4. When a subsequent drop down shows up for severity - select "Fatal"
5. Optionally, check the box next to "Target type" and choose "Database Instance" if your target set includes other targets - this step should not be needed.
6. Everything else should remain the same.
Essentially, the "target down" events come with "Fatal" severity and these "agent down" events come with a "Critical" severity. So this is a way to avoid getting the agent down notifications on databases (or any other targets) while getting the genuine target down notifications. Hope this helps.