Question Regarding Monitoring the pgwatch_metrics Database Itself

[highfortiisss]

Hi,

One of my colleagues asked whether it is possible to monitor the pgwatch_metrics database itself.

I ran some tests, and initially it seems to work. However, after some time, the monitoring process blocks the entire pgwatch system.

Could you please confirm whether it is recommended (or safe) to monitor the metrics database itself?

We have been using pgwatch for a few weeks now to monitor our database, and we are very grateful for your support and assistance.

In the near future, we are planning to roll it out to our clients as well so they can benefit from it too.

Kind regards,

[0xgouda]

the monitoring process blocks the entire pgwatch system.

I don't get this line can you please clarify more?

[highfortiisss]

After some time and after many errors, pgwatch stopped working. I have already redeployed it, but I can add the db again, to reproduce the errors I get when adding a database. If you’re okay with it, I can upload the error details in a few days.

[0xgouda]

Ping, did everything work correctly?

[highfortiisss]

Yes, I’m sorry, I’ve done it three times already, and I don’t understand what’s different this time. Thank you again!

[0xgouda]

Yeah, please do.

Generally Its safe to monitor the pgwatch_metrics database itself (or any database you are using as your sink), actually the demo_metrics database in the demo.pgwatch.com site is just pgwatch_metrics being used as both source and sink

[highfortiisss]

.