2.1. Periodic Nagios Log Parse

---

2.1.1. Description

Nagios-1.2, when compiled with --with-file-perfdata, writes performance data into a file. Perfparse-log2mysql can read that file and save the position of the last read line. This method is also possible with nagios-2.0.

When you don't delete the file with the performance data after you parsed it, be sure that you have defined the Service_Log_Save_Position variable in your Perfparse configuration file, otherwise you will have duplicate entries in your database.

If you enable Service_Log_Save_Position, check if you have devined the Service_Log_Position_Mark_File variable to a path writeable to Perfparse. If not, perfparse will detect an error and stop.

2.2. Nagios Invokes Perfparse

2.3. Periodic User Log Parse

2.4. Pipe to Perfparse

2.5. Perfparse Daemon Server

Perfparsed can run a server to which a client can send performance data. Because the method Pipe to Perfparse is more efficient, we suggest that perfparsed does not read data in a socket on the same host as nagios sending data to perfparsed. Use the pipe instead.

Perfparse-log2socket can be used to send data through the network without the need of the networking abilities of third party tools like database servers. Perfparsed can do the same as a daemon.

2.6. Perfparse Daemon Client

Perfparse-log2* can read data through a socket if the connect to a perfparsed server. They connect to the server and ask for the data between two dates.

Perfparsed must run as a server and have the output_file module enabled to store the performance data in a file. Perfparse-log2* will ask perfparsed to read the file, pass the data through a basic filter (host/metric/key) and send the results to the client who requested them.

5.1. All methods

Next you'll need to enable the Performance Data options in your main Nagios config file.

In the 'PROCESS PERFORMANCE DATA OPTION' section, change the 'process_performance_data' option to '1'. The default is '0' or off.

Then do the specific operations to the chosen method.

Restart Nagios and Performance data should now be enabled. If you find that you don't get data after a few minutes, you may need to make a change from within the Nagios 'Process Info' cgi. To do this, log in to your Nagios site as the administrative user, go to the 'Process Info' page, and at the bottom of the Process Information box, ensure you have:

Performance Data Being Processed?    Yes
			

If Performance Data is not being processed, click the 'Enable performance data' link in the 'Process Commands' box.

If Performance Data is still not being added to the perfdata log files, you probably have not yet installed Nagios plugins that will generate Performance Data. The first version of plugins to support Performance Data is 1.4.0, which at the time of this writing is in an alpha state. Your best bet to ensure that you have a maximum number of Performance Data producing plugins is to use the latest version from CVS.

5.2. Periodic Nagios Log Parse

Then add the following four lines to the 'HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS' section:

xpdfile_host_perfdata_file=/usr/local/nagios/var/hostperf.log
xpdfile_host_perfdata_template=$TIMET$\t$HOSTNAME$\t$OUTPUT$\t$PERFDATA$

xpdfile_service_perfdata_file=/usr/local/nagios/var/serviceperf.log
xpdfile_service_perfdata_template=$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$
			

The last line above may wrap on your screen, please edit accordingly.

5.3. Nagios Invokes Perfparse

Edit misccommands.cfg and add the following :

define command{
        command_name    process-service-perfdata
        command_line    /usr/bin/printf "%b" "$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$\n" | $USER2$/bin/perfparse-log2mysql -c $USER2$/etc/perfparse.cfg
        }
			

$USER2$ is defined in resources.cfg and points to the Perfparse installation directory.

In perfparse.cfg, Service_Log must be defined as "-".

5.4. Periodic User Log Parse

Edit misccommands.cfg and add the following :

define command{
        command_name    process-service-perfdata
        command_line    $USER2$/bin/perfparse_nagios_command.pl $USER2$/var/perfdata-service.log "$TIMET$" "$HOSTNAME$" "$SERVICEDESC$" "$OUTPUT$" "$SERVICESTATE$" "$PERFDATA$"
        }
			

$USER2$ is defined in resources.cfg and points to the Perfparse installation directory.

Edit a script like this :

#!/bin/sh
$USER2=/perfparse/installation/directory

mv ${USER2}/var/perfdata-service.log ${USER2}/var/perfdata-service.log1
cat ${USER2}/var/perfdata-service.log1 | ${USER2}/bin/perfparse-log2mysql -c ${USER2}/etc/perfparse.cfg
rm ${USER2}/var/perfdata-service.log1
			

In perfparse.cfg, Service_Log must be defined as "-".

5.5. Pipe to Perfparse

With nagios-1.2, edit misccommands.cfg and comment out the following definitions for host and service performance data :

define command{
        command_name    process-host-perfdata
			...
        }

define command{
        command_name    process-service-perfdata
			...
        }
			

$USER2$ is defined in resources.cfg and points to the Perfparse installation directory.

Then in the nagios.cfg verify the following are in the file :

cfg_file=/usr/local/nagios/etc/nagios_perfparse.cfg
process_performance_data=1
host_perfdata_command=process-host-perfdata
service_perfdata_command=process-service-perfdata
			

In the perfparse.cfg, make sure the variable Service_Log is set to "|/path/to/perfparse/var/perfdata-service.log".

Permissions for "perfdata-service.log" need to be set as nagios daemon can write to the FIFO.

Finally, in the nagios_perfparse.cfg file :

define command{
        command_name    process-service-perfdata
        command_line    $USER2$/bin/perfparse_nagios_pipe_command.pl $USER2$/var/perfdata-service.log "$TIMET$" "$HOSTNAME$" "$SERVICEDESC$" "$OUTPUT$" "$SERVICESTATE$" "$PERFDATA$"
        }
			

or :

define command{
        command_name    process-service-perfdata
        command_line    $USER2$/bin/perfparse_nagios_pipe_command.pl /usr/local/nagios/var/rw/serviceperf.log "$TIMET$" "$HOSTNAME$" "$SERVICEDESC$" "$OUTPUT$" "$SERVICESTATE$" "$PERFDATA$"
        }
			

5.6. Perfparse Daemon Server

Use_Storage_Socket_Output =         "yes"
Storage_Socket_Output_Host_Name =   "hostname"
Storage_Socket_Output_Port =        "1234"
				

Service_Log =                ""
Server_Port =                "1234" 

				

5.7. Perfparse Daemon Client

Service_Log =                 ">host:port"
				

6.1. Perfparse configuration file

To create a perfparsed.cfg config file using the defaults :

				./perfparsed --show_config   # to see the current config.
			

Run perfparsed, perfparse-log2any or any perfparse-log2* program with --show_config option to see the current config.

Because the output of a Perfparse program is compatible with its configuration file, you can run this to compare to the current perfparse.cfg file :

				./perfparsed --show_config > /var/tmp/perfparse.cfg
			

When /var/tmp/perfparse.cfg is generated, you can edit it and overwrite the old configuration file.

6.2. perfparse-log2mysql

First you should edit 'perfparse.cfg', adding the correct database settings (if using something other than 'nagios' as DB name, username, and password). The options are :

Use_Storage_Mysql (only in perfparsed ; considered as enabled in perfparse-log2mysql)
DB_User
DB_Pass
DB_Name
DB_Host
		

To parse the Performance Data log file using 'Perfparse', use the following command:

./perfparse-log2mysql -r
		

This will parse the data and display a report. Using these:

More options are available, see:

./perfparse-log2mysql --help
		

You can edit your crontab to run perfparse-log2mysql on a regular basis, taking the data from the performance log files and importing it into the DB. For instance, to run PP every 15 minutes, you might use something like the following:

# Run PerfParse every 15 minutes to update Nagios graphs.
15 * * * * /usr/local/nagios/bin/perfparse.sh
		

If you are using method Periodic Nagios Log Parse, PerfParse remembers its position, and will not commit the data until it's ready. Therefore it can be stopped, started, killed, without danger of missing or reprocessing data.

Only 'perfparse-log2mysql' accepts the options mentioned above. If you want to use options when running from cron, you'll need to edit the 'perfparse.sh' script, adding your options to the line that calls 'perfparse-log2mysql'.

Upon upgrading PerfParse, this script is installed as perfparse.sh.example, so if you have edited the original 'perfparse.sh', you may need to add your options to the new file if changes have been made in the distribution version.

To view the your PerfParse graphs, use the same url path as Nagios (http://localhost/nagios/cgi-bin by default) and add /perfparse.cgi at the end.

You can also add a PerfParse link to the Nagios side menu by inserting the following lines of code in path/to/nagios/share/side.html:

tr
    td width=13
        img src="images/greendot.gif" width="13" height="14"
        name="perfparse-dot"
    /td
    td nowrap
        a href="/nagios/cgi-bin/perfparse.cgi?all_bin=1" target="main"
        onMouseOver="switchdot('perfparse-dot',1)"
        onMouseOut="switchdot('perfparse-dot',0)"
        class="NavBarItem"PerfData Graphs/a
    /td
/tr
			

6.3. perfparse-log2socket

Same as perfparse-log2mysql. Options are :

Use_Storage_Socket_Output
Storage_Socket_Output_Host_Name
Storage_Socket_Output_Port
			

6.4. perfparsed

Anyone to write this ?