| From: | Jan Keirse <jan(dot)keirse(at)tvh(dot)com> |
|---|---|
| To: | Andrew Kerber <andrew(dot)kerber(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Required Monitoring |
| Date: | 2017-04-28 14:57:43 |
| Message-ID: | CAH=XL3ebsJqh7U87usmVwM49hCN0C971YAnNMP-XXu4xiC6XGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Apr 28, 2017 at 4:39 PM, 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?
>
>
In addition to what has already been mentioned I also monitor pg_locks .
Not just counts but also mode, duration and non granted locks.
--
**** DISCLAIMER ****
http://www.tvh.com/glob/en/email-disclaimer
"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2017-04-28 16:04:59 | Re: PostgreSQL Required Monitoring |
| Previous Message | Melvin Davidson | 2017-04-28 14:49:30 | Re: PostgreSQL Required Monitoring |