Re: Observability in Postgres

From: Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, stark(at)aiven(dot)io
Subject: Re: Observability in Postgres
Date: 2022-02-14 21:45:51
Message-ID: CANNMO+LU5z-b6+7P-D4yXR=fjEAG9k0AmUKu9NUAt+-crLbFtw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 14, 2022 at 10:15 Greg Stark <stark(at)mit(dot)edu> 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 for Postgres):

https://github.com/CyberDem0n/bg_mon

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joseph Koshakow 2022-02-14 21:57:07 Re: Fix overflow in justify_interval related functions
Previous Message Thomas Munro 2022-02-14 21:35:03 Re: sockaddr_un.sun_len vs. reality