From: | Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Question on Alerts |
Date: | 2025-02-16 16:35:02 |
Message-ID: | 54274170-49f7-4c88-8c23-431d50dd6a9f@dalibo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On 16/02/2025 14:29, sud wrote:
> Hi,
> We are asked to have key monitoring or alerting added to our postgres
> database. And I am thinking of metrics like blocked transactions, Max
> used transaction Ids, Max Active session threshold, Deadlock, Long
> running query, replica lag, buffer cache hit ratio, read/write IOPS or
> latency etc. I have below questions
>
> 1)Below are some which i tried writing, can you please let me know if
> these are accurate?
> 2)How should we be writing the alerting query for deadlock, max used
> transaction ids, read/write IOPS and latency?
> 3)Are there any docs available which have these sample sql queries on
> the pg_* table for these critical alerts which we can easily configure
> through any tool?
> 4)Any other alerts which we should be really having?
>
You should probably look at check_postgres and check_pgactivity. Their
source code contain numerous SQL queries, that could help you write your
own.
Regards.
--
Guillaume Lelarge
Consultant
https://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2025-02-16 17:12:02 | Re: Help in vetting outcome of "vacuumdb --analyze-in-stages" - during DB Upgrade from EC2- PGS - Community Edn ver 13.X to 14.X |
Previous Message | Adrian Klaver | 2025-02-16 16:24:43 | Re: Question on Alerts |