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

Fix CF Dashboard Issues #407

Merged
merged 3 commits into from
Nov 23, 2020
Merged

Fix CF Dashboard Issues #407

merged 3 commits into from
Nov 23, 2020

Conversation

ywei2017
Copy link
Contributor

@ywei2017 ywei2017 commented Oct 28, 2020

At one time (not sure when), many of the CF dashboards no longer show any data (if they ever did). After investigation, I found it was due to the bosh_deployment name being "cf", instead of "cf-[0-9a-f]*". I updated the json files to fix the issue, and also backward compatible. The following is a list of issues and the result with the fix.

Apps:Latency   (no data) [fixed]
Apps: Requests (no data) [fixed]
Apps: System (incomplete data) [fixed]
CF:Organization Memory Quotas (no data for "Organization's Memory Quota Consumption") [fixed]
CF:Route Emitter (no data) [fixed]
CF:Summary (no data for "Users") [fixed]
Component Metrics (no data) [improved]

Also fixed the CF:App:Requests dashboard error when multiple firehose exporters are configured.

Thanks
Yansheng

@ywei2017
Copy link
Contributor Author

Please hold on a little bit. I think I was overly aggressive in the sed replacement. I will do more testing and correct any issues.

@ywei2017
Copy link
Contributor Author

ywei2017 commented Nov 2, 2020

The issue has been fixed and tested. The "sed" issue was more a style than functional, since it was backward compatible.

Thanks
Yansheng

@frodenas frodenas merged commit 6b9c8f1 into cloudfoundry:master Nov 23, 2020
@frodenas
Copy link
Contributor

Thanks @ywei2017!

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

Successfully merging this pull request may close these issues.

2 participants