Re: [External] Re: Nagios Alerting for Postgres Instance.

["Gone, Sajan" <SGone@xxxxxx>]

Thanks Keith and John. 

Thank You,

Sajan Gone

Database Administrator

From: Keith <keith@xxxxxxxxxxx>
Date: Friday, July 21, 2017 at 9:32 AM
To: John Scalia <jayknowsunix@xxxxxxxxx>
Cc: Sajan Gone <sgone@xxxxxx>, pgsql-admin <pgsql-admin@xxxxxxxxxxxxxx>
Subject: [External] Re: Nagios Alerting for Postgres Instance.

Look at the check_postgres module which works well with nagios and provides many of the important metrics to monitor for

https://bucardo.org/wiki/Check_postgres

On Fri, Jul 21, 2017 at 9:16 AM, John Scalia <jayknowsunix@xxxxxxxxx> wrote:

There are dozens of Nagios modules for PostgreSQL. You might be better off deciding what's important to you and look from there

--

Jay

On Jul 21, 2017 8:53 AM, "Gone, Sajan" <SGone@xxxxxx> wrote:

Hi, 

    We have recently deployed a application in production on a Postgres instance which is of community edition. In our enterprise we use Nagios as an alerting system. Generally on our  DB systems we configure to receive alerting/warnings on CPU, memory and other system/OS resources plus DB related issues. 

It would be helpful for me if some one can let me know, what sort of alerting is advisable to configure for Postgres processes.  Any sort of documentation on monitoring would also be very helpful.

 Many thanks in advance. 

Thank You,

Sajan Gone

---

Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LB may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices.

---

Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LB may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices.