FW: Re: Nagios 3.0 SLA Reporting

[Bo Philip Larsen]

Have you been looking at iReport and JasperServer/JasperReport form http://jasperforge.org/sf/projects/ireport it's a good alternative to Crystal Reports.

In the past we have been looking at SLA reporting out of nagios with NDO, but unfortunately we had to stall this project for some time.

Regards,

Bo

-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Mohr James
Sent: 27. maj 2008 18:11
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Nagios 3.0 SLA Reporting

> -----Ursprüngliche Nachricht-----
> Von: Alan Cooper [mailto:ajcooper80 at googlemail.com]
> Gesendet: Dienstag, 27. Mai 2008 16:37
> An: Mohr James
> Cc: nagios-users at lists.sourceforge.net
> Betreff: Re: [Nagios-users] Nagios 3.0 SLA Reporting
>
> Hi,
>
> We had a similar requirement - the quick & dirty way we
> managed to get reports out of Nagios & NDO was to write our
> own DB interogation script in perl (once you have the schema
> from the docs and a copy of SQLyg, the DB is easy to navigate).
>
> To get round the downtime reports for events in the past, I
> wrote a script that simply parsed the nagios logs (scheduled
> downtime events get logged by nagios, just not acted on) with
> epoch times, so it's straightforward to enter a downtime
> start / stop epoch pair, and then for each outage, you can
> check if it occured in a scheduled downtime period.
>
> Would love to hear if anyone has a more elegant solution.

I figured something like that. My boss insists that there must be something out there as there must be other companies with the same problem. That might be true, but it is likely that other companies saw that there was nothing and built their own solution, but never made it available publically.

Using the GUI to record a downtime is much easier than what we do now. Even if it is in the past, it still appears in nagios.log and grepping for SCHEDULE_SVC_DOWNTIME for the given host/service pair is pretty straightforward. Perhaps the "long term" solution would be to change the code (commands.c???) so that each time a downtime is entered it is stored in a DB table at the same time it is written to the command file. At that point all of the checks have been done and all we should need to do is parse the output line and do a DB insert.

I am curious what you use for the actual reporting. Does the "DB interogation script" simply pull the data out of the DB or does it do any reformating? We have been looking at using Crystal Reports, but we currently still have the problem with the outages, but if we figure out how to get it into the DB we should be OK.

Regards,

Jim Mohr



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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