Message-ID: <54274170-49f7-4c88-8c23-431d50dd6a9f@dalibo.com>
Date: Sun, 16 Feb 2025 17:35:02 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Question on Alerts
To: pgsql-general@lists.postgresql.org
References: <CAD=mzVX2xXh0ruTsyXdjtMPEYv=75tN0Gy+Zcs=PaWiCUvS=RA@mail.gmail.com>
Content-Language: fr
From: Guillaume Lelarge <guillaume.lelarge@dalibo.com>
Organization: Dalibo
In-Reply-To: <CAD=mzVX2xXh0ruTsyXdjtMPEYv=75tN0Gy+Zcs=PaWiCUvS=RA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/54274170-49f7-4c88-8c23-431d50dd6a9f%40dalibo.com>
Precedence: bulk

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