Re: PoC: history of recent vacuum/checkpoint runs (using new hooks)
От | Bertrand Drouvot |
---|---|
Тема | Re: PoC: history of recent vacuum/checkpoint runs (using new hooks) |
Дата | |
Msg-id | Z34hXHTUWLuKuFj8@ip-10-97-1-34.eu-west-3.compute.internal обсуждение исходный текст |
Ответ на | Re: PoC: history of recent vacuum/checkpoint runs (using new hooks) (Tomas Vondra <tomas@vondra.me>) |
Список | pgsql-hackers |
Hi, On Tue, Jan 07, 2025 at 10:19:36PM +0100, Tomas Vondra wrote: > On 1/7/25 21:42, Robert Treat wrote: > > On Tue, Jan 7, 2025 at 10:44 AM Bertrand Drouvot > > <bertranddrouvot.pg@gmail.com> wrote: > >> > >> ... > >> > >> Another idea regarding the storage of those metrics: I think that one would > >> want to see "precise" data for recent metrics but would probably be fine with some > >> level of aggregation for historical ones. Something like being able to retrieve > >> "1 day of raw data" and say one year of data aggregated by day (average, maximum, > >> minimum , standard deviation and maybe some percentiles) could be fine too. > >> > > > > While I'm sure some people are ok with it, I would say that most of > > the observability/metrics community has moved away from aggregated > > data storage towards raw time series data in tools like prometheus, > > tsdb, and timescale in order to avoid the problems that misleading / > > lossy / low-resolution data can create. > > > > That's how I see it too. My primary goal is to provide the raw data, > even if it covers only a limited amount of time, so that it can be > either queried directly, or ingested regularly into something like > prometheus. > Okay makes sense. I was thinking about "old habits" that I had but agree that providing raw data is more the way to go nowadays. Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: