Notes on Nagios setup

  5 Responses to “Notes on Nagios setup”

1. 

   Hang says:

   2012-08-01 at 17:42

   Here comes more about nagiosgrapher setup.

   After installation on Ubuntu, it seems several commonly used services were not added to default graph generation, include:

   • load
   • user
   • mysql

   For load and user, it’s pretty simple – copy corresponding check_*.ncfg files from /usr/share/nagiosgrapher/debian/cfg/ngraph.d/standard to /etc/nagiosgrapher/ngraph.d/standard, restart nagiosgrapher service, wait for all machines had done at least one check for both services (so that server’s configuration under /etc/nagios3/conf.d/ngraph/serviceext got updated), then restart nagios3 service to make them show up in the web interface.

   mysql is a tricky thing, it seems check_mysql.ncfg has some problems so you need to tweak it (after copy to /etc/nagiosgrapher/ngraph.d/standard), include:

   • remove the first two sections as there is no such a thing in the stats talking about “diff”
   • rename all ‘mysql-info’ to mysql
   • change Flushtables: to Flush tables: so it matches what exactly in the mysql status
   • change Opentables: to Open tables:, same reason as above
   • (I guess this is optional) change queries: to Slow queries:, and avg: to Queries per second avg:, I believe this is optional because the existing regular expression is runnable, though my changes make it easy to read

   Then just do what I mentioned above for check_load and check_users, it should be there.

   Again there are something new in recent nagios – it can extract data from log (or status message) with graph_log_regex directive, while in the old days one can only read data from performance data parts. Sure you can still read data from value part with graph_perf_regex.
2. 

   Hang says:

   2012-08-01 at 17:44

   Put some keywords here so that people can get help if they are searching online:

   No matching perfdata values found
   check_mysql
   check_mysql.ncfg
   nagios
   nagiosgrapher
3. 

   Hang says:

   2012-08-02 at 14:38

   And it seems service_name in nagios grapher’s ncfg file have to match (partially is ok) service_name in nagios3’s service configuration, otherwise it will be just simply ignored by grapher.
4. 

   Hang says:

   2012-08-02 at 18:14

   Keep posting – I just enabled nagios check for php5-fpm service.

   First you need to enable status page for php5-fpm by uncommenting this in configuration:
   pm.status_path = /status

   Then grab fastcgi client library for php, then just several lines of code:

   $host = 'localhost';
   $port = 9000;
   $options = getopt('H:p:');
   if (isset($options['H']) && !empty($options['H'])) {
       $host = $options['H'];
   }
   if (isset($options['p']) && !empty($options['p'])) {
       $port = $options['p'];
   }
   
   $client = new FCGIClient($host, $port);
   $response = $client->request(
                   array(
                       'REQUEST_METHOD' => 'GET',
                       'SCRIPT_FILENAME' => '/status',
                       'SCRIPT_NAME' => '/status',
                       'QUERY_STRING' => ''
                       ),
                       ''
                   );
   echo str_replace(array("\r", "\n"), " ", $response);

   and things are done. Sure you need to go through all configuration changes for nagios, nrpe, and grapher if you want.
5. 

   Hang says:

   2012-08-03 at 19:05

   It seems check_dns.ncfg has a regex problem – \d should be [\.\d] otherwise it will take 0.011 second as 11 seconds.

Sorry, the comment form is closed at this time.