Discussion: Nagios

[Gavin Grieve [DATACOM]]

We've found that for SNMP trap services, we set the following:
is_volatile                            1              # notify on every failure message, not just when going from OK to failure state
max_check_attempts    1              # notify on the first failure every time
stalking_options                               o,w,c     # log *all* OK, Warning and Critical messages to the Nagios log even if the state hasn't changed

None of these will show all the traps in the host/service display however it will log all the states you have defined to the log file every time the host/service check output is received. Just a warning though - too many hosts/services being stalked can make the log file very big.

--
Gavin Grieve

Systems Management Specialist |  Datacom  |  Datacom House, 68 Jervois Quay, Wellington, 6011, New Zealand
www.datacom.co.nz<http://www.datacom.co.nz/>  |  PO Box 6376, Marion Square, Wellington, New Zealand 6141

From: Manish Kumar [mailto:manikumar85 at gmail.com]
Sent: Thursday, 13 June 2013 9:09 p.m.
To: Nagios Users List
Subject: Re: [Nagios-users] Discussion: Nagios

Hi,

In past I have configured snmp traps from network devices to display in the nagios UI. I have defined only one trap service under a network device which captures all the traps sent for this device in the service, so it will always show you the latest submitted trap/message and send out an alert based on if it's a Warning/Critical trap as may be defined by you in the snmptt config file or the integration script you used.

Since any critical/warning alert logs a ticket on a ticketing system integrated with nagios, we are not so concerned to see all the alerts displayed in one service.

In your case if you always want to display all the incoming traps to be displayed permanently you may need to define multiple trap service under that host and in the integration script you have to map different traps to the different services which you defined. But even in that case you might have defined and mapped a cpu trap service and a fan problem trap service under a host, so the cpu and fan trap will not display in the same service but guess if the new fan trap comes it will again override the old trap and show you in the nagios UI. But in this situation there also a chance to miss a trap or unknow trap which you may not have mapped.

The other way which we are using is I defined a single trap service under a host and I used to reset it to OK after few seconds or minutes of the trap submission so by default it's always OK and once a trap comes it will display it, fire an alert and again rest to OK after few seconds.

Hope it helps you some what :)


On Thu, Jun 13, 2013 at 6:31 AM, Divya Raj <divisback at gmail.com<mailto:divisback at gmail.com>> wrote:
Hi Nagios-Users,

Currently, I am working with Nagios where I have integrated it with a database platform (remote machines) to listen to the alerts and display them in the Nagios Web Interface.

Nagios here runs on RHEL. The remote mahine sends SNMP trap messages (its an external device and not a box so no NRPE/SSH). I've setup SNMPTRAPD in the machine which captures the snmp messages from the box and calls Nagios command to route them to Nagios. For this also, I have defined a trap service to manage the incoming traps from the remote machine.

But, the problem is that only the topmost alert is displayed in the Nagios (in the log as well as in the Nagios Web UI). Is that like till the first one gets cleared the other alerts for the same service don't show up? The thing is that I need all the alerts sent from the remote machine to be sent under one service/host to Nagios.

Any pointers regarding this will be much appreciated.
Thank You.

Regards,
Divya.

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net<mailto:Nagios-users at 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



--
Thanks
Manish Kumar
www.manishkr.com<http://www.manishkr.com>
http://in.linkedin.com/in/manishkumar85
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130614/2d6a6da1/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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