-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pulsar-bookkeeper is not exporting metrics #92
Comments
Hi @leandro-ciandt, I can't seem to reproduce this. What cloud provider are you using to deploy fusion into? I deployed into both EKS and GKE and have bookkeeper metrics appear correctly in prometheus in both environments. |
hi @ian-thebridge-lucidworks, i'm using my own kubernetes cluster. i'm not using EKS, GKE or AKS. i noticed that for bookkeeper, the created service is not exposing port 8000 (which should be used by exporter), it's exposing just the client port (3181). |
@leandro-ciandt , okay thank you. I see that the service only exposes is the bookkeeper instance that you are seeing as down in the prometheus UI running and in a |
@ian-thebridge-lucidworks, thanks for replying. also i'm using my own Prometheus and i'm not deploying it with the Fusion cluster. so, i'm not using the pod's annotations to configure the targets. i'm creating the ServiceMonitors for that and it's expected that the exporters in the pods being exposed the same way as you guys are doing for other services. otherwise, i'll need to create a specific service targeting the bookkeeper exporter for that and i don't believe that's the way. p.s.: all the services and pods are up and running. also, if a do a port-forward to the pods i can see the metrics being generated. |
What is the issue?
What is the problem?
What is expected?
--
p.s.: for all other five endpoints (api-gateway, indexing, pulsar-broker, query-pipeline and solr), the metrics are being scrapped fine.
The text was updated successfully, but these errors were encountered: