-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix grafana dashboard and clarify dashboard usage more clearly. #543
Conversation
@fangfenghuang Can you help review this pr? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix some http url
@jiangsanyin This relabeling should be consistent with the configurations for It would be helpful to include this information in the documentation, as users unfamiliar with the Prometheus stack may struggle to configure everything correctly on the first attempt |
Have you created and applied the ServiceMonitor as depicted in dashboard.md or dashboard_cn.md?node_name is added after this is done.
#apply the file hami-device-plugin-svc-monitor.yaml |
@jiangsanyin It’s important to document this configuration to ensure it aligns with the relabeling setup for |
…he image display problem in document; Change deployment/values.yaml before deploying dcgm-exporter. Signed-off-by: jiangsanyin <1327212357@qq.com>
Ok, thanks to your review. Certain relabelings configurations in serviceMonitor for dcgm-exporter has been added in dashboard_cn.md and dashboard.md, please check! |
/lgtm |
1 similar comment
/lgtm |
Signed-off-by: jiangsanyin 1327212357@qq.com
What type of PR is this?
/kind bug
What this PR does / why we need it:
fix grafana dashboard and clarify dashboard usage more clearly. Thanks "fangfenghuang (https://github.com/fangfenghuang)" for your help
Which issue(s) this PR fixes:
Fixes #498 #468
Special notes for your reviewer:
Does this PR introduce a user-facing change?: