log based monitoring Postgresql
Posted: Sun May 21, 2017 9:18 am
i am using the below configuration for the log based monitoring but there was miss of alarm no alarm was reported for the Postgres down attached are the relevant files.
Can you let me know the reason for such possible miss of alarms from nagiosXI
postgress check is as shown below on the node
[nagios@hnrbt10 conf]$ cat PostgreSQL.conf
$seekfilesdir = '/home/nagios/logfile_basedir/tmp';
$protocolsdir = '/home/nagios/logfile_basedir/tmp';
$scriptpath = '/home/nagios/bin';
#$MACROS = { CL_DISK01 => "/dev/dsk/c0d1", CL_DISK02 => "/dev/dsk/c0d2" };
@searches = (
{
tag => 'PostgreSQL down',
criticalpatterns => ['PostgreSQL is down'|'PostgreSQL is already stopped'|'Forcing msPostgresql away from hnrbt10 after 1000000 failures'|'Forcing msPostgresql away from hnrbt11 after 1000000 failures'] ,
options => 'sticky=1800,noprotocol,report=long,allyoucaneat',
logfile => '/var/log/messages'
#rotation => 'SUSE',
}
);
As i tested it from GUI it gave me the following output PFA
Can you let me know the reason for such possible miss of alarms from nagiosXI
postgress check is as shown below on the node
[nagios@hnrbt10 conf]$ cat PostgreSQL.conf
$seekfilesdir = '/home/nagios/logfile_basedir/tmp';
$protocolsdir = '/home/nagios/logfile_basedir/tmp';
$scriptpath = '/home/nagios/bin';
#$MACROS = { CL_DISK01 => "/dev/dsk/c0d1", CL_DISK02 => "/dev/dsk/c0d2" };
@searches = (
{
tag => 'PostgreSQL down',
criticalpatterns => ['PostgreSQL is down'|'PostgreSQL is already stopped'|'Forcing msPostgresql away from hnrbt10 after 1000000 failures'|'Forcing msPostgresql away from hnrbt11 after 1000000 failures'] ,
options => 'sticky=1800,noprotocol,report=long,allyoucaneat',
logfile => '/var/log/messages'
#rotation => 'SUSE',
}
);
As i tested it from GUI it gave me the following output PFA