Is your feature request related to a problem? Please describe.
Long story short: Prometheus exporter responds to GET requests on any path/endpoint:
- /metrics
- /liveness
- /my/pets/123
- /
In my case, I didn't notice a missing update in a k8s manifest - custom listener on port 12321 used to handle both metrics and liveness/readiness. I've switched liveness to the application port, and kept 12321 for Prometheus exporter. I forgot to update the probes, and the exporter responded with 200 OK to probe calls on /liveness and /readiness, thus hiding the missconfiguration.
Describe the solution you'd like
New enviromental variable:
OTEL_EXPORTER_PROMETHEUS_PATH=/metrics
or:
OTEL_EXPORTER_PROMETHEUS_PATHS=/metrics,/foo,/
Also, 404 response for requests that do not match the endpoint.
Describe alternatives you've considered
No response
Additional context
No response
Is your feature request related to a problem? Please describe.
Long story short: Prometheus exporter responds to GET requests on any path/endpoint:
In my case, I didn't notice a missing update in a k8s manifest - custom listener on port 12321 used to handle both metrics and liveness/readiness. I've switched liveness to the application port, and kept 12321 for Prometheus exporter. I forgot to update the probes, and the exporter responded with 200 OK to probe calls on /liveness and /readiness, thus hiding the missconfiguration.
Describe the solution you'd like
New enviromental variable:
OTEL_EXPORTER_PROMETHEUS_PATH=/metricsor:
OTEL_EXPORTER_PROMETHEUS_PATHS=/metrics,/foo,/Also, 404 response for requests that do not match the endpoint.
Describe alternatives you've considered
No response
Additional context
No response