I would stop doing the time-consuming ticket integration (or whatever is
taking up the time) from within the notification command itself. I don't
think you need to build a separate notification server - after all,
notification logic is one of the things Nagios does best - but I do think
you could b
A typical first tier notification goes to 20 people. One of those will
be a pager, and is very simple.
The rest are fairly complex.
Notifications include a link to existing and recent tickets in our
ticketing system (this also allows me to not send a ticket opening
notification if a ticket al
What kind of notifications are you doing and how many are you sending out?
Why does a notification cycle take 9 seconds to complete?
On Sat, Jan 23, 2010 at 12:13 AM, Mike Lindsey wrote:
> What kind of options does one have, if your master nagios server is
> getting overloaded?
>
> I have half a
What kind of options does one have, if your master nagios server is
getting overloaded?
I have half a dozen slaves doing polling, submitting passive check
results back via send_nsca. The master does no active polling, just
event processing, notifications, and web ui.
Under normal circumstance
