public inbox for [email protected]
help / color / mirror / Atom feedFrom: Guillaume Lelarge <[email protected]>
To: [email protected]
Subject: Re: Question on Alerts
Date: Sun, 16 Feb 2025 17:35:02 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAD=mzVX2xXh0ruTsyXdjtMPEYv=75tN0Gy+Zcs=PaWiCUvS=RA@mail.gmail.com>
References: <CAD=mzVX2xXh0ruTsyXdjtMPEYv=75tN0Gy+Zcs=PaWiCUvS=RA@mail.gmail.com>
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
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Question on Alerts
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox