Skip to content
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

Open
ciandt-leandro opened this issue Apr 9, 2020 · 4 comments
Open

pulsar-bookkeeper is not exporting metrics #92

ciandt-leandro opened this issue Apr 9, 2020 · 4 comments

Comments

@ciandt-leandro
Copy link

What is the issue?

  • the 'customize_fusion_values.yaml' example is showing that for 'pulsar-bookkeeper' we have the default endpoint '/metrics' on port '8000' for monitoring, but the 'pulsar-bookkeeper' service is not exposing that port, it's only exposing 'client:3181' port.

What is the problem?

  • on Prometheus targets i'm not seeing the '/metrics' endpoint 'UP' and the metrics are not being got by the scraper.

What is expected?

  • have the port '8000' exposed on 'pulsar-bookkeeper' service for '/metrics' endpoint and Prometheus targets reaching the metrics responses and labels.

--

p.s.: for all other five endpoints (api-gateway, indexing, pulsar-broker, query-pipeline and solr), the metrics are being scrapped fine.

@ian-thebridge-lucidworks
Copy link
Collaborator

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.

@ciandt-leandro
Copy link
Author

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).

@ian-thebridge-lucidworks
Copy link
Collaborator

ian-thebridge-lucidworks commented Apr 14, 2020

@leandro-ciandt , okay thank you.

I see that the service only exposes 3181, but that shouldn't be a problem that stops the metrics from being scraped. Prometheus is targeting the bookkeeper pods directly and not going through the kubernetes service mechanism, so it shouldn't matter that we don't expose port 8000 in the service.

is the bookkeeper instance that you are seeing as down in the prometheus UI running and in a Ready state?

@ciandt-leandro
Copy link
Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants