Actions
Bug #47997
closedmgr/dashboard: OSD disk performance statistics not working in grafana
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Monitoring
Target version:
% Done:
0%
Source:
Community (user)
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When we want to view the disk statistics we get the following message :
found duplicate series for the match group {device=\"dm-6\", instance=\"ceph_cluster\"} on the right hand-side of the operation: [{__name__=\"ceph_disk_occupation\", ceph_daemon=\"osd.41\", db_device=\"/dev/dm-33\", device=\"dm-6\", exported_instance=\"*OSD HOST NAME*\", instance=\"ceph_cluster\", job=\"ceph\"}, {__name__=\"ceph_disk_occupation\", ceph_daemon=\"osd.50\", db_device=\"/dev/dm-7\", device=\"dm-6\", exported_instance=\"imx-ceph-am11-osd-02\", instance=\"ceph_cluster\", job=\"ceph\"}];many-to-many matching not allowed: matching labels must be unique on one side
Updated by Lenz Grimmer over 3 years ago
- Translation missing: en.field_tag_list set to grafana, monitoring
- Subject changed from OSD disk performance statistics not working in grafana to mgr/dashboard: OSD disk performance statistics not working in grafana
- Description updated (diff)
Updated by Patrick Seidensal over 3 years ago
- Status changed from New to In Progress
- Assignee set to Patrick Seidensal
Updated by Patrick Seidensal over 3 years ago
Updated by Patrick Seidensal over 3 years ago
- Is duplicate of Bug #47334: mgr/dashboard: many-to-many matching not allowed: matching labels must be unique on one side added
Updated by Patrick Seidensal over 3 years ago
- Is duplicate of deleted (Bug #47334: mgr/dashboard: many-to-many matching not allowed: matching labels must be unique on one side)
Updated by Patrick Seidensal over 3 years ago
- Related to Bug #47334: mgr/dashboard: many-to-many matching not allowed: matching labels must be unique on one side added
Updated by Patrick Seidensal over 3 years ago
- Pull request ID set to 37792
After Ceph has been updated, the cephadm mgr module will need a restart to load the new code:
ceph mgr module disable cephadm && sleep 2 && ceph mgr module enable cephadm
To recreate Prometheus' configuration file run:
ceph orch redeploy prometheus
Furthermore note that even after the fix has correctly been applied and the configuration file has been updated, the error will continue to persist for requests made that have a time span from before the fix has been applied. To verify please select a time span like "last 5 minutes", and make sure the fix has correctly been applied for that time.
Updated by Patrick Seidensal over 3 years ago
- Status changed from In Progress to Fix Under Review
Updated by Sebastian Wagner over 3 years ago
- Status changed from Fix Under Review to Resolved
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 148 to Monitoring
Actions