Re: PostgreSQL Required Monitoring

From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Andrew Kerber
Sent: Friday, April 28, 2017 12:58 PM
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] PostgreSQL Required Monitoring

Attention: This email was sent from someone outside of Perceptron. Always exercise caution when opening attachments or clicking links from unknown senders or when receiving unexpected emails.

Yes, that was the first item on my list (disk space)...

On Fri, Apr 28, 2017 at 11:56 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com<mailto:scott(dot)marlowe(at)gmail(dot)com>> wrote:
On Fri, Apr 28, 2017 at 8:39 AM, Andrew Kerber <andrew(dot)kerber(at)gmail(dot)com<mailto: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.

--
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

And there lies another difference with Oracle: Postgres does not allocate disk space for data files “in advance” (like Oracle does).

Regards,
Igor Neyman