What I would like to do, for my network printers, switches, routers, and some
other devices, is add more information to the extended info page. I have been
playing around with notes and to get decently readable output, I end up with a
bunch of ugly looking HTML which I have been duplicating
On Tue, Nov 16, 2010 at 4:33 PM, Mark A. Lappin ma...@lmfj.com wrote:
What I would like to do, for my network printers, switches, routers, and some
other devices, is add more information to the extended info page. I have
been playing around with notes and to get decently readable output, I
Mark A. Lappin wrote:
What I would like to do, for my network printers, switches, routers, and
some other devices, is add more information to the extended info page. I have
been playing around with notes and to get decently readable output, I end up
with a bunch of ugly looking HTML which I
Hi,
Here is the problem I'm trying to solve. We have services that
have a set maintenance window, for example every Tuesday from 13:30 to 14:00.
So to stop Nagios from sending notifications during this maintenance window I
have created a time period that excludes tuesday
After some testing, it looks like it will only re-notify after receiving
another passive check result. It won't simply re-notify because it's still in
a non-ok state after the notification_interval has expired. So to combat this
I just used the check freshness attribute to re-execute my
I noticed something curious. It looks like Nagios 3.2.3 is making
on-demand host checks faster than the retry_interval should allow. The
interval_length is set to 60 and the retry_interval is set to 1. Nagios
and the plugins were compiled from source on CentOS 5.5 x64.
I'm not sure if this
toner part number etc; routers nearest service center, circuit identifier,
etc. Works great, hard to maintain.
Agreed. IMHO information like that shouldn't be kept in the Nagios config. A
trick we've used a few times is to have a wiki installed, then have notes_url
be
Please set your MUA to wrap long lines at something sensible (72 chars
is the standard, I think).
On 11/16/2010 09:44 PM, Chung, Jeff wrote:
Hi, Here is the problem I'm trying to solve. We have services that
have a set maintenance window, for example every Tuesday from 13:30
to 14:00. So to
On 11/16/2010 09:59 PM, Chris Beattie wrote:
I noticed something curious. It looks like Nagios 3.2.3 is making
on-demand host checks faster than the retry_interval should allow. The
interval_length is set to 60 and the retry_interval is set to 1. Nagios
and the plugins were compiled from
On 11/16/2010 10:43 PM, Andreas Ericsson wrote:
Please set your MUA to wrap long lines at something sensible (72 chars
is the standard, I think).
On 11/16/2010 09:44 PM, Chung, Jeff wrote:
Hi, Here is the problem I'm trying to solve. We have services that
have a set maintenance window, for
Hi all,
I noticed the same strange behavior, but I don't think it's the right
behavior.
Operating in this way, a linkDown trap will be notified only once (in
fact the sender device will generate a single trap in response to state
change).
Is it possibile to modify this behavior?
Hall, JC
Not using exclude works perfectly.
-Original Message-
From: Andreas Ericsson [mailto:a...@op5.se]
Sent: Tuesday, November 16, 2010 4:56 PM
To: Nagios Users List
Cc: Chung, Jeff
Subject: Re: [Nagios-users] Next possible notification time bug
On 11/16/2010 10:43 PM, Andreas Ericsson wrote:
Escalations can resolve this - if you set an escalation to trigger at
notification 1 and set a re-notify interval in the escalation you will
be re-notified at the set interval while the service remains in the
configured alarm state.
- Max
On Tue, Nov 16, 2010 at 4:41 PM, Alberto Menichetti
Just use the built in feature for this: is_volatile.
See http://nagios.sourceforge.net/docs/2_0/volatileservices.html
Regards,
Martin Melin
On Tue, Nov 16, 2010 at 10:41 PM, Alberto Menichetti
alb.meniche...@tai.it wrote:
Hi all,
I noticed the same strange behavior, but I don't think it's
In my opinion it'useless in this scenario; the official doc says:
Volatile services differ from normal services in three important ways.
*/Each time/ they are checked* when they are in a hard non-OK state, and
the check returns a non-OK state (i.e. no state change has occurred)...
But in my
15 matches
Mail list logo
