On 2/16/25 12:31, sud wrote:
On Sun, Feb 16, 2025 at 10:05 PM Guillaume Lelarge
mailto:guillaume.lela...@dalibo.com>> wrote:
You should probably look at check_postgres and check_pgactivity. Their
source code contain numerous SQL queries, that could help you write
your
own.
> On Feb 16, 2025, at 12:31, sud wrote:
> where exactly I can get the source code for check_postgres and
> check_pgactivity?
https://github.com/bucardo/check_postgres
https://github.com/OPMDG/check_pgactivity
While the list is happy to help, I should note that I found these by searching
fo
On Sun, Feb 16, 2025 at 10:05 PM Guillaume Lelarge <
guillaume.lela...@dalibo.com> wrote:
>
> 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.
>
>
Thank you very much. I am a bit ne
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
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,
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