dragonflydb
ServiceMonitor doens't work out of the box
Hello. I've deployed the dragonfly-operator Helm chart with the following values:
serviceMonitor:
enabled: true
But my VMAgent can't scrape metrics:
unexpected status code returned when scraping "http://10.244.2.242:8443/metrics": 400; expecting 200; response body: "Client sent an HTTP request to an HTTPS server.\n"
Thanks for reporting!
I can try testing it out, but in the meanwhile we have something tested around metric collection of Dragonfly at https://www.dragonflydb.io/docs/managing-dragonfly/operator/prometheus-guide
We are facing the same problem.
As far as I see, the ServiceMonitor is targeting the port 8443 where as in the pod configuration the parameter --metrics-bind-address=127.0.0.1:8080 is set with a other port.
I have this problem too
To fix it, you need to change the logic:
- start operator pod with
-metrics-bind-address=0.0.0.0:8080 - this port(8080) must set in ports of deployment
- serviceMonitor is targeted to this port
And why don't you use podMonitor instead serviceMonitor? This operator deployment doesn't seem to require the service, as it doesn't accept traffic.
Just ran into this issue, is there a workaround for now until a fix is merged?
Run into the same issue. Is there any intention of fixing this? I believe it should be as simple as changing the binding address to 0.0.0.0:8080 in case servicemonitor is enabled
Same questions: Why not use a PodMonitor - and how can Prometheus connect when the bind address is set to 127.0.0.1?
