MIME-Version: 1.0
References: <CAD=mzVXXQq6c4_L_fcG2GeYWRuAuEh+t5XLuCGaPj+1iFSCSPw@mail.gmail.com>
In-Reply-To: <CAD=mzVXXQq6c4_L_fcG2GeYWRuAuEh+t5XLuCGaPj+1iFSCSPw@mail.gmail.com>
From: Julien Rouhaud <rjuju123@gmail.com>
Date: Sat, 27 Apr 2024 22:24:48 +0800
Message-ID: <CAOBaU_ayPvKRb_RRg93UiXc65xJnGhww8RAnrqHbNVyg7pT+hw@mail.gmail.com>
Subject: Re: Monitoring and debugging historical performance
To: sud <suds1434@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAOBaU_ayPvKRb_RRg93UiXc65xJnGhww8RAnrqHbNVyg7pT%2Bhw%40mail.gmail.com>
Precedence: bulk

Hi,

On Sat, Apr 27, 2024 at 10:01=E2=80=AFPM sud <suds1434@gmail.com> wrote:
>
> Hi All,
> While looking option to see how one can monitor database performance for =
debugging into historical database performance issues (historical database =
wait events , CPU/memory utilization in past, query execution times in past=
 , executions paths at any point in time in past etc), It appears there exi=
sts some options as i googled in the internet like pg_sentinel,pgsnapper, p=
g_collector. Wanted to check, if anybody used these utilities and suggest a=
ny of them to use for a longer term use?

I would personally recommend PoWA
(https://powa.readthedocs.io/en/latest/), as it handles everything you
require.  Disclairmer: I'm the main author of this tool