Changes for Prometheus3 - BBS config for cf_exporter and custom.rules.yml#582
Merged
benjaminguttmann-avtq merged 5 commits intocloudfoundry:masterfrom Jan 13, 2026
Merged
Conversation
benjaminguttmann-avtq
approved these changes
Jan 13, 2026
Contributor
benjaminguttmann-avtq
left a comment
There was a problem hiding this comment.
lgtm ,thank you @cweibel
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problems:
cf_application_instances_runningthecf_exporterneeds to be configured to connect to BBS.cf_exporteralready supports scraping from BBS if certain environment variables are set, however the spec that configures this on the Prometheus side was missing./var/vcap/jobs/prometheus2/config/custom.rules.ymlinprometheus.ymleven though the file is rendered correctly to/var/vcap/jobs/prometheus/config/custom.rules.yml. This results in the custom rules file being ignored. Referenced in issue Prometheus3 custom_rules hardcoded to prometheus2 path #580Solutions:
cf_exporter.bbs.ca,cf_exporter.bbs.cert,cf_exporter.bbs.keywhich are supplied from CF credhub variablediego_bbs_client.ca,diego_bbs_client.certificate,diego_bbs_client.private_key. When combined withdiego_bbs_api_urlthese are the 4 values required to have the cf_exporter scrape the BBS endpoint.prometheus.ymlto point to the new job location with the renaming of jobs from Prometheus2 to Prometheus3