[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [hobbit] EXHOST usage

Henrik Stoerner wrote:

Henrik,

This will work nicely, but I also realized something else...while the IGNORE option will indeed ignore the alert, the main display will still show red for that service. So while no pages may go out, anyone who monitors the page visually will still think there is a problem.

The optimal soultion I think, would be a "MAINT" option, where you could specify time periods that a host and or service automatically goes into maintenance mode. This way no pages go out, and the display has the proper visual indication that the host has been administratively disabled. Something like:
MAINT HOST=dataproc1.mydomain.com SERVICE=cpu TIME=*:0600:1000

It might even be nice to be able to tack on a REASON="Some reason here", that gets put on the maint page, but if that is too difficult could just use a generic reason like "administratively disabled".

-Charles

Note: the way I handle this in BigBrother is via an exclude rule, basically when you define a rule with a ! in front of it, it removes that host/service from the FINAL match list. Hopefully you can implement something in Hobbit for a similar effect.



What I've done now (you can grab it from the snapshot that is generated
later tonight - 5 hours from now) would allow you to setup those rules
like this:

# Default rule (1)
HOST=$ALL_HOSTS SERVICE=* COLOR=red
	# Ignore "cpu" alerts from dataproc1 in the morning
	IGNORE HOST=dataproc1.mydomain.com SERVICE=cpu TIME=*:0600:1000
	# During office hours, alert to the mailbox.
	MAIL alert (at) mydomain.com TIME=*:0800:1700
	# Outside office hours, mail alerts to a different address (4)
	MAIL alternate (at) mydomain.com TIME=*:1700:0800
	# Outside office hours, send to my cell phone (5)
	MAIL mycell (at) cellphone.com FORMAT=sms DURATION>30 TIME=*:1700:0800

"IGNORE" is a special recipient definition - like MAIL and SCRIPT - so
you can apply all of the host-, service- and time-filters etc to it.
If the IGNORE recipient triggers, it doesn't trigger an alert - and it
stops Hobbit looking for more recipients (like the STOP flag).