Metrics endpoint is not exposed by Service #61
Comments
To let us able to scrape metrics from the Operator e.g. with a ServiceMonitor we need to have a Service which provides named port close CrunchyData#61 Signed-off-by: Alex Szakaly <[email protected]>
To let us able to scrape metrics from the Operator e.g. with a ServiceMonitor we need to have a Service which provides named port close CrunchyData#61 Signed-off-by: Alex Szakaly <[email protected]>
To let us able to scrape metrics from the Operator e.g. with a ServiceMonitor we need to have a Service which provides named port close CrunchyData#61 Signed-off-by: Alex Szakaly <[email protected]>
To let us able to scrape metrics from the Operator e.g. with a ServiceMonitor we need to have a Service which provides named port close CrunchyData#61 Signed-off-by: Alex Szakaly <[email protected]>
|
@alex1989hu These are controller metrics -- is there anything specific you are looking to collect? |
For now, there are no specific metrics but it is enabled in PGO. Did not check PGO source code whether we set additional metrics or not. Propose to expose it (see PR) or disable metrics endpoint in PGO |
To let us able to scrape metrics from the Operator e.g. with a ServiceMonitor we need to have a Service which provides named port close CrunchyData#61 Signed-off-by: Alex Szakaly <[email protected]>
|
Hey Alex, just wanted to let you know that I've added this (and the related PR) to our backlog to make a decision on whether we want to expose those metrics or disable them by default. |
|
you should also add Manifests (Pod or ServiceMonitor) for Prometheus-Operator (like in #94 ) for the Operator to scrape that metrics. And maybe PrometheusRules with a default set of AlertingRules. |
|
I'll confess I'd love to see this in the |
I found during Postgres Operator startup that the metrics server is binded to 8080 port but unfortunately it is not exposed by k8s Service.
Actual log line:
Prometheus metrics are available at :8080/metrics URL.
The text was updated successfully, but these errors were encountered: