NagiosGrapher: How do the links work?

[Arno Lehmann]

Hello,

On 1/26/2006 7:23 AM, Hugo van der Kooij wrote:
> On Thu, 26 Jan 2006, Arno Lehmann wrote:
> 
> 
>>On 1/25/2006 11:42 PM, Hugo van der Kooij wrote:
>>
>>
>>>(In fact I am puzzled by much more but let's take it one step at the
>>>time.)
>>
>>Let nagiosgrapher write a detailed log and observe what happens in
>>there. tail -f is just the tool for that...
> 
> 
> It is this log that got me puzzled most of all. It seems the default
> samples don't work too well. Only the HTTP details are currently resulting
> in some logs.

Well, modifying nagiosgraphers configuration to your needs does take 
some time. In fact I had to taylor all the entries concerning data 
acquisition to my needs. Now, I don't know if you know how to handle 
regular expressions, but these and the service names are the lines that 
probably need to be modified to your setup.

If you posted one of the entries not working and the corresponding 
output from the check plugin someone, perhaps even I, might help you more.

For example, from my local system a service check I set up yesterday:
In the status detail page, I see the output from the checks:

> CPU=0%;10;20;; Storage=26853376;58720256;67108864;; Objects=3244;1032192;1048576;; HitRatio=0%;;;; IPs=125;3584;4096;; Clients=3;1792;2048;;

The service is called "Squid status" and one of the corresponding 
entries in my nagiosgrapher configuration is

> define ngraph{
>         service_name            Squid status
>         graph_perf_regex        HitRatio=(\d+\.?\d*)%
>         graph_value             Hits
>         graph_units             %
>         graph_legend            Hit ratio
>         rrd_plottype            LINE1
>         rrd_color               0000FF
>         lowerlimit              0
>         page                    ProcessState
> }

Which produces the expected results, along with the links to the 
graphics cgi in the service overview and -detail pages in Nagios' frontend.

With lots of logging during set up, I got these log entries from 
nagiosgrapher when it encountered a service check for "Squid status" the 
first time:

> 2006-01-25 22:30:28 RRD: rrdtool create /var/lib/nagios/rrd/balrog/0023bdc292ea73c8d13bcb38a0c107d8.rrd --step= DS:CPU:GAUGE:600:U:U DS:Hits:GAUGE:600:U:U DS:Clients:GAUGE:600:U:U DS:IPs:GAUGE:600:U:U DS:Stored:GAUGE:600:U:U DS:Objs:GAUGE:600:U:U RRA:AVERAGE:0.5:5:600 RRA:MAX:0.5:5:600 RRA:MIN:0.5:5:600 RRA:AVERAGE:0.5:30:600 RRA:MAX:0.5:30:600 RRA:MIN:0.5:30:600 RRA:AVERAGE:0.5:120:600 RRA:MAX:0.5:120:600 RRA:MIN:0.5:120:600 RRA:AVERAGE:0.5:1440:600 RRA:MAX:0.5:1440:600 RRA:MIN:0.5:1440:600
> 2006-01-25 22:30:28 RRD: [balrog][Squid status]:/var/lib/nagios/rrd/balrog/0023bdc292ea73c8d13bcb38a0c107d8.rrd - successfully created!
> 2006-01-25 22:30:28 SERVICEEXT: [balrog][Squid status]:Entry in serviceextinfo not exists, create NEW!
> 2006-01-25 22:30:28 VALUES: [balrog][Squid status]: Stored=24567808 IPs=111 Hits=72 CPU=0 Objs=2964 Clients=3
> 2006-01-25 22:30:28 RRD: rrdtool update /var/lib/nagios/rrd/balrog/0023bdc292ea73c8d13bcb38a0c107d8.rrd --template=Stored:IPs:Hits:CPU:Objs:Clients N:24567808:111:72:0:2964:3

One thing to notice: If you modify the data capture setup, you will have 
to manually modify the corresponding rrd file (or delete it and let 
nagiosgrapher automatically recreate it) because the template for 
inserting doesn't fit to the rrd file any more.

Let's see if you get that set up...

Arno

> Hugo.
> 

-- 
IT-Service Lehmann                    al at its-lehmann.de
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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