[Nagios-users] Best Practice: Forgotten Acknowledgements
Hello list, from time to time you may acknowledge a problem without solving it at once. This will result in forgotten acknowledgements. What do you do to resolve this issue? Ist there anything existing which parses the statufiles and writes a mail once a week as a reminder (cron-job)? Greetz, Andre -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ 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] Best Practice: Forgotten Acknowledgements
Am Montag, den 01.11.2010, 12:50 -0400 schrieb Chris Beattie: Acknowledgements add comments to hosts and services, so you could just set yourself a reminder to occasionally check the comments link in the side bar and look for anything that's getting stale. Yes, but this would enforce a human not to forget things. I tend to believe something automatic is more reliable than a human ;) Greetz, Andre -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ 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
[Nagios-users] $NOTIFICATIONISESCALATED$
Hello lIST, I want to use the macro $NOTIFICATIONISESCALATED$ in my notifications, I want to have it displayed within my jabber-notifications. Unfortunately this macro seemes not to work: Notification Type: PROBLEM Service: ssh Host: somehost State: CRITICAL for 0d 0h 0m 52s Address: 192.168.0.100 Info: Connection refused Date/Time: Mon Apr 6 16:05:19 CEST 2009 ACK by: Comment: Escalated: $ I have found the same problem on http://www.nagios-portal.org/wbb/index.php?page=ThreadpostID=81210 (German forum) I have enable_environment_macros=1 in my config. Any ideas? Greetz, Andre -- ___ 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
[Nagios-users] Bug, Feature or Layer 8 problem?
Hello List,
we are generating the timeperiods for our oncall-support via script.
Sometimes, one line of the configfile semes to be ignored:
define timeperiod{
timeperiod_name andre_2pikett_week
alias Andre 2nd Pikett
2009-03-29 09:00-24:00
2009-03-30 00:00-09:00
2009-03-30 18:00-24:00
2009-03-31 00:00-09:00
}
In this case there is a problem with the second definition of
2009-03-30, it will be ignored. So I will not get any messages between
18:00 and 24:00.
Of course, if i I use
2009-03-30 00:00-09:00,18:00-24:00
it will work.
Unfortunately there is no message during startup of nagios, stating that
it will ignore one line of my configfile.
Is this a bug or a feature? ;)
I am using Version 3.0.6 from Debian lenny.
--
Mit freundlichen Grüssen
Andre Timmermann
Nine Internet Solutions AG, Albisriederstr. 243c, CH-8047 Zuerich
--
___
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
