Thanks Alan and Mark for your responses....
I'm not familiar with NDOUtils -- do both your approaches require
that? Also, what are good frontends or Perl modules for utlizing
the NDO data once it's in the database?
Thanks,
Peter
Begin forwarded message:
From: Alan Cooper <[email protected]>
I've spent an unfathomable amount of time trying to achieve similar.
In the end, I installed NDOUtils and built some rough scripts to
interogate the database pulling stats based on (for my needs, but it
could be altered) hostgroup and working out availability.
For stuff that's not my fault, e.g. customer issue such a power
onsite, we schedule downtime. Downtime within scheduled downtime is
not counted in the availability report.
An added complication is that if you enter a downtime period in the
past (i.e. retrospectiove downtime at some point after the event when
you've correctly established blame) Nagios does not add it to the NDO
database - I had to scrip up something to parse the nagios log files
from the command submission for the downtime period and manually add
these periods to the database myself prior to reporting.
HTH
Begin forwarded message:
From: Marc Powell <[email protected]>
Date: March 17, 2009 12:15:56 PM EDT
To: nagios-users Listserv <[email protected]>
Subject: Re: [Nagios-users] Added "Blame" to availability reports
On Mar 17, 2009, at 8:57 AM, Peter Burkholder wrote:
The one thing that's requested is the ability to report on
availability that's 'Our Fault' vs. availability thats 'Vendor
Fault'.
1) Is anyone here aware of any add-ons that would provide the ability
to ascribe downtime periods to a cause, then provide reports on
downtime due to that cause?
Not I (but they may exist).
2) If I were to write my own add-on, what would be the right
approach?
If I were to develop an external app to do this for a single service,
I'd approach it by using an event_handler to log down and up
timestamps to a database, then add comments to the database associated
with those events.
3) Could I get the requested availability reporting if I were to
create some weird timeperiod like
'24x7_except_the_times_we_screwed_up', where that timeperiod were to
use 24x7, with exceptions for the downtime that were our fault?
Not that I can envision.
The simplest, nagios-native approach I can think of is to just add a
comment to the service with the detail you want. At the end of each
month, review the comments for the service then remove them.
--
Marc
--
Peter Burkholder
AARP | Web Strategy & Operations
601 E Street, NW | Washington, DC 20049
email: [email protected] | aim: peterbtech | phone: 202-434-3530
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Nagios-users mailing list
[email protected]
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
