Re: Observability in Postgres

Hi, On Wed, Feb 16, 2022 at 12:48:11AM -0500, Greg Stark wrote: > 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

Re: Observability in Postgres

On Wed, 2022-02-16 at 02:10 -0500, Greg Stark wrote: > On Tue, 15 Feb 2022 at 17:37, Magnus Hagander wrote: > > > But I think you'll run into a different problem much earlier. Pretty > > much everything out there is going to want to speak http(s). How are > > you going to terminate that, especial

Re: Observability in Postgres

Hi, On Mon, Feb 14, 2022 at 03:15:14PM -0500, Greg Stark wrote: > > [...] > 2) SQL connections are tied to specific databases within a cluster. > Making it hard to get data for all your databases if you have more > than one. The exporter needs to reconnect to each database. > > 3) The exporter nee

Re: Observability in Postgres

On Tue, 15 Feb 2022 at 17:37, Magnus Hagander wrote: > > On Tue, Feb 15, 2022 at 11:24 PM Greg Stark wrote: > > > > On Tue, 15 Feb 2022 at 16:43, Magnus Hagander wrote: > > I really don't see the problem with having the monitoring on a different port. > > I *do* see the problem with having a dif

Re: Observability in Postgres

On Tue, 15 Feb 2022 at 22:48, Stephan Doliov 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 bac

Re: Observability in Postgres

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

Re: Observability in Postgres

On Tue, Feb 15, 2022 at 11:24 PM Greg Stark wrote: > > On Tue, 15 Feb 2022 at 16:43, Magnus Hagander wrote: > > > > On Tue, Feb 15, 2022 at 1:30 PM Dave Page wrote: > > > > > > - Does it really matter if metrics are exposed on a separate port from > > > the postmaster? I actually think doing th

Re: Observability in Postgres

On Tue, 15 Feb 2022 at 16:43, Magnus Hagander wrote: > > On Tue, Feb 15, 2022 at 1:30 PM Dave Page wrote: > > > > - Does it really matter if metrics are exposed on a separate port from the > > postmaster? I actually think doing that is a good thing as it allows use of > > alternative listen add

Re: Observability in Postgres

On Tue, Feb 15, 2022 at 1:30 PM Dave Page wrote: > > Hi Greg, > > On Mon, 14 Feb 2022 at 20:16, Greg Stark wrote: >> >> So I've been dealing a lot with building and maintaining dashboards >> for (fleets of) Postgres servers. And it's a pain. I have a few >> strongly held ideas about where the pai

Re: Observability in Postgres

On 2/15/22 07:30, Dave Page wrote: On Mon, 14 Feb 2022 at 20:16, Greg Stark > wrote: So I've been dealing a lot with building and maintaining dashboards for (fleets of) Postgres servers. And it's a pain. I have a few strongly held ideas about where the pain poin

Re: Observability in Postgres

Hi Greg, On Mon, 14 Feb 2022 at 20:16, Greg Stark wrote: > So I've been dealing a lot with building and maintaining dashboards > for (fleets of) Postgres servers. And it's a pain. I have a few > strongly held ideas about where the pain points are and what the right > ways to tackle them are. Som

Re: Observability in Postgres

On Mon, Feb 14, 2022 at 10:15 Greg Stark wrote: > > For now my approach is to implement a background worker that listens > on a new port and is basically its own small web server with shared > memory access This reminds me bg_mon (included into Spilo, docker image used by Zalando operator