id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc
338	Easier viewing of scripts alert status	adehnert		"Often, a single trigger will set off a bunch of nagios alerts at once (for example, if the load gets high enough that it isn't responding to NRPE probes). This produces a storm of zephyrs. When the services come back, it produces another storm of zephyrs. It's not immediately obvious whether ''all'' the services came back, or just most of them. (Of course, there are methods for figuring out which ones came back --- ""finger broken@sipb-noc"", looking at the sipb-nagios website, or counting, for example.) It would be nice if this were more blatantly obvious. (Perhaps each nagios zephyr should list the currently-broken services?)"	enhancement	new	minor		internals