Re: [Nagios-users] Notifications on passive service checks

2010-11-16 Thread Alberto Menichetti

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 wrote:

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 external script and 
feed the passive check result into nagios and thus re-sending a non-ok 
notification at what would have been the interval for notifications.

So technically my external scripts are running at every interval to check the 
freshnes, not only when it's called for by my event_handler from another active 
service check...  which I'm ok with.

-Original Message-
From: Andreas Ericsson [mailto:a...@op5.se] 
Sent: Friday, November 12, 2010 5:00 AM

To: Nagios Users List
Cc: Hall, JC
Subject: Re: [Nagios-users] Notifications on passive service checks

On 11/11/2010 11:27 PM, Hall, JC wrote:
  

Is it accurate that Nagios will only send 1 notification for a
passive service check?

IE, the notification_interval definition for a passively checked
service won't instruct Nagios to re-send a notification such as with
actively checked services?




To be honest, I haven't got the faintest idea. An educated guess is
that it will re-send the notification if it receives another passive
check-result and enough time has passed though, or that it simply
re-sends the notification when enough time has passed.

If you try and find out, let me know either way and I'll amend the
docs.

  



--
TAI S.r.l.

Alberto Menichetti
Area Mercato - Ingegneria dei Sistemi
System Engineer

50141 Firenze - Via Pazzagli, 2 
Voice: +39 055 42661 - Fax +39 055 4266356 
56125 Pisa - Viale Gramsci, 12 
Voice: +39 050 220221 - Fax: +39 050 24421 


e-mail: alb.meniche...@tai.it
http://www.tai.it

---
COMUNICAZIONE AI SENSI LEGGE 196/03
Il presente messaggio di posta elettronica viene inviato al Vostro indirizzo 
email, che abbiamo acquisito da Vostre Visite, da incontri commerciali, elenchi 
di pubblico dominio, Vostre precedenti comunicazioni. Il Vostro dato in 
questione e' in possesso di TAI S.r.l., che lo ha immagazzinato in formato 
elettronico. Tali informazioni non saranno divulgate a terzi. Se desiderate 
verificare, cancellare o modificare i dati in nostro possesso, inviate fax al 
numero 0554266356.


--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2  L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Re: [Nagios-users] Notifications on passive service checks

2010-11-16 Thread Alberto Menichetti

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 setup passive services are never checked (they are  trap 
collectors,  and  my devices send  traps on state change).

Let's suppose this scenario:

1. interface Gi0/1 on catalyst switch goes down
2. the switch sends a linkDown trap to the manager
3. the manager decodes the event and submits the alert via nagios.cmd
4. the service associated with that switch changes it's state to critical
5. the contacts are notified (the first time)
6. that's all...contacts will never be notified again until a new 
linkDown trap is processed


Martin Melin wrote:

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 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 wrote:

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 external
script and feed the passive check result into nagios and thus re-sending a
non-ok notification at what would have been the interval for notifications.

So technically my external scripts are running at every interval to check
the freshnes, not only when it's called for by my event_handler from another
active service check...  which I'm ok with.

-Original Message-
From: Andreas Ericsson [mailto:a...@op5.se]
Sent: Friday, November 12, 2010 5:00 AM
To: Nagios Users List
Cc: Hall, JC
Subject: Re: [Nagios-users] Notifications on passive service checks

On 11/11/2010 11:27 PM, Hall, JC wrote:


Is it accurate that Nagios will only send 1 notification for a
passive service check?

IE, the notification_interval definition for a passively checked
service won't instruct Nagios to re-send a notification such as with
actively checked services?



To be honest, I haven't got the faintest idea. An educated guess is
that it will re-send the notification if it receives another passive
check-result and enough time has passed though, or that it simply
re-sends the notification when enough time has passed.

If you try and find out, let me know either way and I'll amend the
docs.



--
TAI S.r.l.

Alberto Menichetti
Area Mercato - Ingegneria dei Sistemi
System Engineer

50141 Firenze - Via Pazzagli, 2
Voice: +39 055 42661 - Fax +39 055 4266356
56125 Pisa - Viale Gramsci, 12
Voice: +39 050 220221 - Fax: +39 050 24421

e-mail: alb.meniche...@tai.it
http://www.tai.it

---
COMUNICAZIONE AI SENSI LEGGE 196/03
Il presente messaggio di posta elettronica viene inviato al Vostro indirizzo
email, che abbiamo acquisito da Vostre Visite, da incontri commerciali,
elenchi di pubblico dominio, Vostre precedenti comunicazioni. Il Vostro dato
in questione e' in possesso di TAI S.r.l., che lo ha immagazzinato in
formato elettronico. Tali informazioni non saranno divulgate a terzi. Se
desiderate verificare, cancellare o modificare i dati in nostro possesso,
inviate fax al numero 0554266356.


--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2  L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null




--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2  L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please