From: | Keith <keith(at)keithf4(dot)com> |
---|---|
To: | Kiriakos Georgiou <kg(dot)postgresql(at)olympiakos(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: monitoring solutions |
Date: | 2016-02-29 22:17:51 |
Message-ID: | CAHw75vuaPONe_9-QiaZb7GDG_pURMwJ=-6nts4QrqWkTX-SJ_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Feb 29, 2016 at 4:01 PM, Kiriakos Georgiou <
kg(dot)postgresql(at)olympiakos(dot)com> wrote:
> Hello,
>
> I am reviewing the database monitoring solutions listed at
> https://wiki.postgresql.org/wiki/Monitoring for use with our aviation
> related project.
> I’m interested in a slick dashboard that can quickly pinpoint potential
> issues. So far nothing has jumped at me as an obvious choice.
>
> One thing I should mention is that it can’t be a SaaS solution like
> https://www.vividcortex.com/monitoring/postgres/
> It must be able to host the solution.
>
> Do you have any suggestions? Something you have successfully used for a
> while.
>
> thanks,
> Kiriakos
>
I'd say the easiest, complete, self-hosted monitoring solution for postgres
to get up and running would be Nagios (https://www.nagios.org/) +
check_postgres (https://bucardo.org/wiki/Check_postgres) Even when I'm
setting up other monitoring solutions, the list of things monitored by
check_postgres is a great guideline to follow to make sure you've got the
important stuff covered. Plus nagios provides you with other normal system
monitoring things that are also important to database health (CPU, RAM,
disk usage, etc).
Keith
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Baptiste Vedel | 2016-03-02 07:04:52 | To avoid a database shutdown, execute a database-wide VACUUM |
Previous Message | Kiriakos Georgiou | 2016-02-29 21:01:23 | monitoring solutions |