| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Andrew Kerber <andrew(dot)kerber(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Required Monitoring |
| Date: | 2017-04-28 16:56:39 |
| Message-ID: | CAOR=d=1OcOyA+Oy2h3s-QOrTkZVb48sGTH1450w7Dih_TbeZ8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Apr 28, 2017 at 8:39 AM, Andrew Kerber <andrew(dot)kerber(at)gmail(dot)com> wrote:
> I am a fairly experienced Oracle DBA, and we are starting to move in to the
> PostgreSQL world. I would expect the standard monitoring items are required
> for mission critical postgres apps, Ie, disk space, wal log space, log
> monitoring, process counts,software running, connection available on the
> correct port, CPU usage.
>
> Are there additional PostgreSQL specific items that need to be monitored?
> if so, what items?
Amid all the other recommendations standard OS level monitoring is a
good idea. You don't wanna run out of space on drives etc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Kerber | 2017-04-28 16:58:13 | Re: PostgreSQL Required Monitoring |
| Previous Message | Igor Neyman | 2017-04-28 16:53:07 | Re: PostgreSQL Required Monitoring |