monitoring PostgreSQL

okmeter.io is good (though it's cloud-based and costs some money), I'm
using it and definitely can recommend.

There much more tools, see: https://wiki.postgresql.org/wiki/Monitoring

On Mon, Jul 24, 2017 at 4:27 AM, PAWAN SHARMA <er.pawanshr0963@gmail.com>
wrote:

pgbadger is a very nice reporting tool, overall, albeit not exactly at the system side, but more to the DBA side.
For system level monitoring maybe take a look here : https://wiki.postgresql.org/wiki/Monitoring#check_postgres .
Also you might want to write a script that parses logs for FATAL and PANIC and sends out emails.

On 24/07/2017 14:27, PAWAN SHARMA wrote:

Hi All,

Please provide me a list of tools which we can use for monitoring PostgreSQL.

-Monitor all the services and health of server
-Able to send critical and warning alert on mail.

OS: Redhat-7
PostgreSQL Version: 9.5.7

-Pawan

--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

We use nagios for all alerting, it'll do what you need.

Tim Clarke

On Mon, Jul 24, 2017 at 5:20 PM, Tim Clarke <tim.clarke@manifest.co.uk>
wrote:

We use nagios for all alerting, it'll do what you need.

Tim Clarke

On 24/07/17 12:38, Achilleas Mantzios wrote:

pgbadger is a very nice reporting tool, overall, albeit not exactly at
the system side, but more to the DBA side.
For system level monitoring maybe take a look here :
https://wiki.postgresql.org/wiki/Monitoring#check_postgres .
Also you might want to write a script that parses logs for FATAL and
PANIC and sends out emails.

On 24/07/2017 14:27, PAWAN SHARMA wrote:

Hi All,

Please provide me a list of tools which we can use for monitoring
PostgreSQL.

-Monitor all the services and health of server
-Able to send critical and warning alert on mail.

OS: Redhat-7
PostgreSQL Version: 9.5.7

-Pawan

--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

Hi Tim,

Thanks for update,

Please share the steps, how to configure Nagios??

On Mon, Jul 24, 2017 at 5:50 PM, PAWAN SHARMA <er.pawanshr0963@gmail.com>
wrote:

On Mon, Jul 24, 2017 at 5:20 PM, Tim Clarke <tim.clarke@manifest.co.uk>
wrote:

We use nagios for all alerting, it'll do what you need.

Tim Clarke

On 24/07/17 12:38, Achilleas Mantzios wrote:

pgbadger is a very nice reporting tool, overall, albeit not exactly at
the system side, but more to the DBA side.
For system level monitoring maybe take a look here :
https://wiki.postgresql.org/wiki/Monitoring#check_postgres .
Also you might want to write a script that parses logs for FATAL and
PANIC and sends out emails.

On 24/07/2017 14:27, PAWAN SHARMA wrote:

Hi All,

Please provide me a list of tools which we can use for monitoring
PostgreSQL.

-Monitor all the services and health of server
-Able to send critical and warning alert on mail.

OS: Redhat-7
PostgreSQL Version: 9.5.7

-Pawan

--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

Hi Tim,

Thanks for update,

Please share the steps, how to configure Nagios??

Hi Tim,

Facing below issue

[abc@test:/home/psharm89/nrpe-2.15]#
Redirecting to /bin/systemctl restart xinetd.service
Failed to restart xinetd.service: Unit xinetd.service failed to load: No
such file or directory.
[abc@test:/home/psharm89/nrpe-2.15]#

[abc@test:/home/psharm89/nrpe-2.15]#
#-> less /etc/xinetd.d/nrpe
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port = 5666
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}

On 24/07/17 14:47, PAWAN SHARMA wrote:

Hi Tim,

Facing below issue

[abc@test:/home/psharm89/nrpe-2.15]#
Redirecting to /bin/systemctl restart xinetd.service
Failed to restart xinetd.service: Unit xinetd.service failed to load:
No such file or directory.
[abc@test:/home/psharm89/nrpe-2.15]#

[abc@test:/home/psharm89/nrpe-2.15]#
#-> less /etc/xinetd.d/nrpe
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port = 5666
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}

xinetd is broken? restore the config from backup.

Tim

On Mon, Jul 24, 2017 at 7:28 PM, Tim Clarke <tim.clarke@manifest.co.uk>
wrote:

On 24/07/17 14:47, PAWAN SHARMA wrote:

Hi Tim,

Facing below issue

[abc@test:/home/psharm89/nrpe-2.15]#
Redirecting to /bin/systemctl restart xinetd.service
Failed to restart xinetd.service: Unit xinetd.service failed to load:
No such file or directory.
[abc@test:/home/psharm89/nrpe-2.15]#

[abc@test:/home/psharm89/nrpe-2.15]#
#-> less /etc/xinetd.d/nrpe
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port = 5666
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}

xinetd is broken? restore the config from backup.

Tim

#-> /etc/init.d/nagios restart
Restarting nagios (via systemctl): Job for nagios.service failed because
the control process exited with error code. See "systemctl status
nagios.service" and "journalctl -xe" for details.

On 24/07/17 15:01, PAWAN SHARMA wrote:

On Mon, Jul 24, 2017 at 7:28 PM, Tim Clarke <tim.clarke@manifest.co.uk
<mailto:tim.clarke@manifest.co.uk>> wrote:

On 24/07/17 14:47, PAWAN SHARMA wrote:

Hi Tim,

Facing below issue

[abc@test:/home/psharm89/nrpe-2.15]#
Redirecting to /bin/systemctl restart xinetd.service
Failed to restart xinetd.service: Unit xinetd.service failed to

load:

No such file or directory.
[abc@test:/home/psharm89/nrpe-2.15]#

[abc@test:/home/psharm89/nrpe-2.15]#
#-> less /etc/xinetd.d/nrpe
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port = 5666
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}

xinetd is broken? restore the config from backup.

Tim

#-> /etc/init.d/nagios restart
Restarting nagios (via systemctl): Job for nagios.service failed
because the control process exited with error code. See "systemctl
status nagios.service" and "journalctl -xe" for details.

And what do

"systemctl status nagios.service"
and
"journalctl -xe"

tell you?

Tim