No data points from cf-exporter in Prometheus 25.0.0

[san4ever]

We have upgraded our PAS from 2.4 to 2.6 . We have update bosh proemetheus from 24.1.0 to 25.0.0 . We are not getting metrics for cloudfoundry latency metrics. Could you help us in fixing this. Let us know any information needed

[roberto-yslas]

I had this problem as well. I found some documentation that indicated that you need to assign your cf- deployment name as the value for metron_deployment_name in your deployment. In our case we had to add scrape config for the cf_exporter since our foundation wasn't responding very fast.

  scrape_interval: 2m
  scrape_timeout: 1m

I will say this is very strange because I have several implementations of prometheus and the two I have running on 25 - on one I didn't have to make these changes. On the other I did.

[shanmuksandeep]

Hey @roberto-yslas Can you help me where can i get name for metron_deployment_name

[shanmuksandeep]

Hi @roberto-yslas Here is snipped for firehose_exporter and cf_exporter job . Let us know for any changes i have modify in these jobs

[roberto-yslas]

snip from the monitor-cf.yml operator file:

• type: replace path: /instance_groups/name=prometheus2/jobs/- value: name: cf_exporter release: prometheus properties: cf_exporter: cf: api_url: https://api.((system_domain)) client_id: cf_exporter client_secret: "((uaa_clients_cf_exporter_secret))" deployment_name: ((metron_deployment_name)) metrics: environment: "((metrics_environment))" skip_ssl_verify: ((skip_ssl_verify))

for the interpolated variable metron_deployment_name you should put your cf-(guid) of your CF deployment in your foundation.

bosh -e (your-foundation-env) deployments | grep cf

HTH, Rob

[roberto-yslas]

e.g.

[bldbxops@peplap03496 prometheus25]$ bosh -e dev-director deployments | grep cf

cf-a66dec9161eca2c38d11 backup-and-restore-sdk/1.12.0 bosh-azure-hyperv-ubuntu-xenial-go_agent/250.99 - latest cf-autoscaling/219

metron_deployment_name=cf-a66dec9161eca2c38d11

[san4ever]

Hi @roberto-yslas We even tried to give complete cf deployment name. But data is not populating

[san4ever]

Hi @roberto-yslas Could you give insights on this. Tried changing metron name with cf deployment didn;t solve the issue yet Also can you please review this below issue, in case you faced in your foundation https://github.com/bosh-prometheus/prometheus-boshrelease/issues/359

[roberto-yslas]

It is not the deployment_name that you need to modify; that is only a label. It is the metron_deployment_name that you need to set to your cf deployment.

[san4ever]

Hi @roberto-yslas Yes Instead of metron_deployment_name --> We gave cf-deployment name. Also have attached the snippet in above comment. Could you also suggest other option so that i will tweak into

[roberto-yslas]

That's what worked for me - don't know why it's not working for you.

[san4ever]

Can you also confirm your PAS and Prometheus version please

On Thu, 28 Nov, 2019, 10:42 AM roberto-yslas, notifications@github.com wrote:

That's what worked for me - don't know why it's not working for you.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bosh-prometheus/prometheus-boshrelease/issues/340?email_source=notifications&email_token=AHA6E4QNO4NHZPZELXDSLKLQV5HLNA5CNFSM4I363ITKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFLOW2Y#issuecomment-559344491, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHA6E4RVNZV4VGU2PDYQAULQV5HLNANCNFSM4I363ITA .

[benjaminguttmann-avtq]

@san4ever does the issue still persist?

[benjaminguttmann-avtq]

Closed due to inactivity; Please feel free to re-open if issue still persists