From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | "Gone, Sajan" <SGone(at)lb(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Nagios Alerting for Postgres Instance. |
Date: | 2017-07-21 13:16:19 |
Message-ID: | CABzCKRDU7qHBGH_J09QWK2bPJwOUgqzEAk2xS-m0eLa3VuUSXw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)lb(dot)com> 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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Keith | 2017-07-21 13:32:52 | Re: Nagios Alerting for Postgres Instance. |
Previous Message | Gone, Sajan | 2017-07-21 12:52:04 | Nagios Alerting for Postgres Instance. |