![]() |
![]() |
Subject: | Notifications not emailing.. |
Author: | [Not Specified] |
Posted: | 2014-03-12 16:09 |
Ok I setup a trigger like:
ServerDownPower
enabled
all
Summary contains is DOWN!
Location contains Weidman, MI
Device Class contains /Server
User is set to my with my email address (i did a user test earlier and the test email came through)
The Notification is setup:
Power_Down
enabled
send only on initial occurence
Delay 300 seconds (to take into account for a normal reboot, 5 min should be plenty)
Triggers: ServerDownPower
Subscribers:
user me write yes manage yes
I cannot find the link but a trigger/notif tutorial I found via google said that using the Summary was what you;d use to catch events in Zenoss.. by the text in the event maybe.
If not then what did I do wrong here
Subject: | Settings |
Author: | Mark H |
Posted: | 2014-03-13 03:59 |
Hi Bicarbonate, so your email settings are correct, it may be your trigger. You have told Zenoss to find all those events at once, else do not send an email, i.e. for an email to be sent the summary text must contain 'DOWN!' (it is case sensitive by the way), AND it must be in location 'Weidman, MI' (exact match and case sensitive), AND it must be in Device class '/Server'.
Unless all of those parameters are met TOGETHER, your email will not be sent.
Subject: | Handsy is correct, it sounds |
Author: | [Not Specified] |
Posted: | 2014-03-13 09:17 |
Handsy is correct, it sounds like the events aren't match the trigger. I suggest you start with something very basic and go from there. Example below:
Trigger:
Rule: Severity equals critical
Users: Check all 3 and add user at the bottom
Notification:
Delay: 300 seconds
Trigger: Assign the new simple trigger you created
Content: Leave as-is
Subscribers: Check all 3 and add user at the bottom
Then once you have the basic setup working, start making it more advanced and specific. That way you can rule out any email type issues!
Hydruid
Subject: | make sure that when you |
Author: | Andrew Kirch |
Posted: | 2014-03-13 14:25 |
make sure that when you create the notification you assign the trigger to the notification. 90% of the time when one of my triggers don't fire it's because I overlooked this.
zeneventd.log might also help you with what's going on
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
Subject: | Thanks guys.. I had added a |
Author: | [Not Specified] |
Posted: | 2014-03-14 07:45 |
Thanks guys.. I had added a Mint desktop to my servers list to test this.. obviously so I didnt have to shut down or take offline a real server :)
Ok so I made teh changes ya'll suggested, I simplified the trigger to only look for Severity of Critical. An email notif came through when I unplugged this test host.
So I will add one criteria at a time and try to get back to the ruleset that I'm wanting...
Subject: | Ok I changed the Severity to |
Author: | [Not Specified] |
Posted: | 2014-03-14 07:59 |
Ok I changed the Severity to Summary contains DOWN!... notif came thru.
Subject: | Back to original trigger |
Author: | [Not Specified] |
Posted: | 2014-03-14 08:48 |
Back to original trigger criteria and it works. I think my issues with testing this specific host was forgetting to set the location :hides:
Thanks guys!
< |
Previous Package 'zenoss' isn't signed with proper key |
Next Duplicate/Splintered Devices via ZenDMD - Help! |
> |