From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | sud <suds1434(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Question on Alerts |
Date: | 2025-02-16 16:24:43 |
Message-ID: | 70589303-83d2-46f3-b192-6b4682db7b75@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/16/25 05: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?
Somewhere to start:
https://wiki.postgresql.org/wiki/Category:Administration#Routine_maintenance_and_monitoring
> Regards
> Yudhi
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2025-02-16 16:35:02 | Re: Question on Alerts |
Previous Message | Adrian Klaver | 2025-02-16 16:19:35 | Re: Help in vetting outcome of "vacuumdb --analyze-in-stages" - during DB Upgrade from EC2- PGS - Community Edn ver 13.X to 14.X |