Bug #47323
closed
monitoring: Use null yaxes min for OSD read latency
Added by Seena Fallah over 3 years ago.
Updated about 3 years ago.
Backport:
nautilus, octopus
Description
According to seriesOverrides that negative-Y for read param there shouldn't be a minimum for yaxes
- Category set to 148
- Status changed from New to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Target version set to v16.0.0
- Copied to Backport #47995: nautilus: monitoring: Use null yaxes min for OSD read latency added
- Copied to Backport #47996: octopus: monitoring: Use null yaxes min for OSD read latency added
- 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".
- Project changed from mgr to Dashboard
- Category changed from 148 to Monitoring
Also available in: Atom
PDF