Project

General

Profile

Actions
Copy link

Bug #51990

closed

monitoring/grafana/cluster: use per-unit max and limit values

Added by Ernesto Puerta over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Aashish Sharma
Category:
Monitoring
Target version:
-
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
pacific,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
41880
Crash signature (v1):
Crash signature (v2):

Description

Description of problem

The value we get is a perunit, so the limits and the max value should
be over 1, not 100. Note that the value being shown was correct, it
was the gauge that was not showing the correct indicators.

Related issues 2 (0 open — 2 closed)

Copied to Dashboard - Backport #51992: pacific: monitoring/grafana/cluster: use per-unit max and limit valuesResolvedLaura PaduanoActions
Copied to Dashboard - Backport #51993: octopus: monitoring/grafana/cluster: use per-unit max and limit valuesResolvedLaura PaduanoActions
Actions
Copy link
 #1

Updated by Backport Bot over 2 years ago

  • Copied to Backport #51992: pacific: monitoring/grafana/cluster: use per-unit max and limit values added
Actions
Copy link
 #2

Updated by Backport Bot over 2 years ago

  • Copied to Backport #51993: octopus: monitoring/grafana/cluster: use per-unit max and limit values added
Actions
Copy link
 #3

Updated by Loïc Dachary over 2 years ago

  • Target version deleted (v16.2.6)
Actions
Copy link
 #4

Updated by Loïc Dachary over 2 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF