From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Stephan Doliov <stephan(dot)doliov(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, David Fetter <david(at)fetter(dot)org>, stark(at)aiven(dot)io |
Subject: | Re: Observability in Postgres |
Date: | 2022-02-16 05:48:11 |
Message-ID: | CAM-w4HOd0+17zMFct0JVJCdnfJkkLx=DT3SMcNHs9q2fja6zag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 15 Feb 2022 at 22:48, Stephan Doliov <stephan(dot)doliov(at)gmail(dot)com> wrote:
>
> I am curious what you mean by standard metrics format? I am all for standards-based but what are those in the case of DBs. For environments where O11y matters a lot, I think the challenge lies in mapping specific query executions back to system characteristics. I am just thinking aloud as a newbie to this community.
I was about to reply simply that the standard the open source world is
coalescing around is OpenMetrics. This is basically a codification of
the prometheus format with some extra features.
But on further thought I think what you're asking is whether there are
standard database metrics and standard names for them. A lot of this
work has already been done with pg_exporter but it is worth looking at
other database software and see if there are opportunities to
standardize metrics naming for across databases.
I don't really expect a lot of deep examples of that though. As soon
as you dig under the surface the differences quickly add up so you'll
have different labels with different semantics. But sure, it would be
nice if you could do simple high level queries like "number of active
connections" using the same metrics on mysql, postgres, and ...
whatever.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2022-02-16 05:57:56 | Re: make tuplestore helper function |
Previous Message | Michael Paquier | 2022-02-16 05:43:08 | Re: make tuplestore helper function |