Metrics endpoint for internal pgwatch metrics #1174
Replies: 7 comments
-
|
Hello, we have some, e.g. It's more system connected though |
Beta Was this translation helpful? Give feedback.
-
|
That would be a great starting point. I am having problems accessing these though, there is no api endpoint on 9178 for me when running pgwatch. The documentation mentions the --sink option for prometheus, but from my understanding that is for saving the scraped metrics to a prometheus database and not about the internal metrics from pgwatch. |
Beta Was this translation helpful? Give feedback.
-
|
All metrics are served to prometheus, just different prefixes. |
Beta Was this translation helpful? Give feedback.
-
|
and yes, one needs to run |
Beta Was this translation helpful? Give feedback.
-
|
Because for me, pgwatch does not even listen at all on port 9187. Only 8080 for the webui. So "--sink=prometheus" just gives me an error because there is nothing, it cant connect. Edit: Forget what i wrote, argument was at the wrong position in the pgwatch call and needed to be 0.0.0.0... |
Beta Was this translation helpful? Give feedback.
-
|
How do you run pgwatch? Show me the line, please. Do you specify |
Beta Was this translation helpful? Give feedback.
-
|
Fixed it already, the argument needed to be 0.0.0.0 and not localhost in our k8s environment. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
It would be handy to have a prometheus metrics endpoint from pgwatch itself. Useful metrics would be:
Describe the solution you'd like
Metrics endpoint (/metrics or /prometheus) which provides internal pgwatch metrics
Beta Was this translation helpful? Give feedback.
All reactions