Seeking Assistance for Pgwatch3 Custom Setup and Missing Features

[MichalBartos]

Hello all,
First, I would like to thank you for this amazing tool. It is very helpful for us :).

Now, to my questions. I'm trying to set up Pgwatch3 as a custom installation (unfortunately, using Docker is not possible for me). I'm missing features like HTTPS for the web UI (https://pgwat.ch/v3.0/concept/web_ui.html). I tried to use a similar configuration as in Pgwatch2, but it doesn't work:

Environment="PW_WEBSSL=true"
Environment="PW_WEBCERT=<path_to_cert_file>"
Environment="PW_WEBKEY=<path_to_key_file>"

Also, I'm unable to set up/access Gatherer health check (for Docker installation mentioned here https://pgwat.ch/v3.0/tutorial/docker_installation.html#available-docker-images it seems more likely for Pgwatch2). On Pgwatch2, it was enabled on the pgwatch2 daemon. Is this JSON accessible via the web UI on Pgwatch3? If yes, on what link? I've found /, /sources, /metrics, /presets, and /logs in the documentation and in the source on GitHub.

It would be nice to have those features in Pgwatch3.

Thank you.

Best regards, Michal

[pashagolub]

Hi Michal.

I'm missing features like HTTPS for the web UI

Thanks for your kind words. We don't have SSL implementation yet. But I think it's not the hardest thing to implement.

Also, I'm unable to set up/access Gatherer health check

Oh, yes. My fault. I forgot to update that part of the documentation. So we have two REST API endpoints on the web UI port:

• /liveness
• /rediness

/liveness will return 200 OK is pgwatch is started, and /readiness will return 200 OK when pgwatch finished initialization and ready to fetch metrics.

[MichalBartos]

Thank you for quick reply :)

[pashagolub]

Speaking of HTTPS, why don't you want to put your pgwatch behind reverse proxy like nginx?

[MichalBartos]

Let's say, that processes of using any extra SW on our server are very complicated. We must manage it by ourself, but we don't have direct access to configs, certificates or logs on server. This means a thing that can be done in a few minutes could take days. We have an access only to user running pgwatch and its configuration. So we prefer build in solution then using nginx or other proxy.

[ondar]

How can you have anything done in so restrictive environment? 😁 If you really need HTTPS inside pgwatch, you can always contribute.

[pashagolub]

I want to clarify my position. I'm not against the TLS implemented in pgwatch itself, I just wanna know the whole story from the user perspective