Project

General

Profile

Actions
Copy link

Bug #45068

closed

mgr/dashboard: Prometheus query error while filtering values in the metrics of Pools and OSDs

Added by Avan Thakkar about 4 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Avan Thakkar
Category:
Monitoring
Target version:
Ceph - v16.0.0
% Done:

0%

Source:
Development
Tags:
Backport:
nautilus, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
Ceph - v14.2.9, Ceph - v15.2.2, Ceph - v16.0.0
ceph-qa-suite:
Pull request ID:
34532
Crash signature (v1):
Crash signature (v2):

Description

In Overall Performance of OSDs and Pools while trying to 'Filter out value' or 'Filter for value' in the table, data disappears and some parse error is shown like parse error at char 122: unexpected "{" in grouping opts, expected ")"

Files

Download all files
Screenshot from 2020-04-13 15-07-39.png (126 KB) Screenshot from 2020-04-13 15-07-39.png parse error in Pools overall performance Avan Thakkar, 04/13/2020 09:38 AM
Screenshot from 2020-04-13 16-08-38.png (220 KB) Screenshot from 2020-04-13 16-08-38.png parse error in OSDs overall performance Avan Thakkar, 04/13/2020 10:38 AM
Screenshot from 2020-04-21 22-02-37.png (173 KB) Screenshot from 2020-04-21 22-02-37.png parse error in RBD images overall performance Avan Thakkar, 04/21/2020 04:33 PM

Related issues 3 (1 open — 2 closed)

Related to Dashboard - Bug #46272: mgr/dashboard: workaround needed for ad-hoc filter of the tables Need More Info

Actions
Copied to Dashboard - Backport #46312: nautilus: mgr/dashboard: Prometheus query error while filtering values in the metrics of Pools and OSDsResolvedAvan ThakkarActions
Copied to Dashboard - Backport #46313: octopus: mgr/dashboard: Prometheus query error while filtering values in the metrics of Pools and OSDsResolvedAvan ThakkarActions
Actions
Copy link
 #1

Updated by Avan Thakkar about 4 years ago

  • File deleted (Screenshot from 2020-04-12 02-08-40.png)
Actions
Copy link
 #2

Updated by Avan Thakkar about 4 years ago

Avan Thakkar wrote:

In Overall Performance of OSDs and Pools while trying to 'Filter out value' or 'Filter for value' in the table, data disappears and some parse error is shown like parse error at char 122: unexpected "{" in grouping opts, expected ")"

Actions
Copy link
 #3

Updated by Avan Thakkar about 4 years ago

Avan Thakkar wrote:

In Overall Performance of OSDs and Pools while trying to 'Filter out value' or 'Filter for value' in the table, data disappears and some parse error is shown like parse error at char 122: unexpected "{" in grouping opts, expected ")"

Actions
Copy link
 #4

Updated by Volker Theile about 4 years ago

  • Status changed from New to Fix Under Review
  • Assignee set to Avan Thakkar
  • Backport set to nautilus, octopus
  • Pull request ID set to 34532
Actions
Copy link
 #5

Updated by Volker Theile about 4 years ago

  • Category set to 148
  • Target version set to v16.0.0
  • Source set to Development
  • Affected Versions v14.2.9, v15.2.2, v16.0.0 added
Actions
Copy link
 #7

Updated by Lenz Grimmer almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #8

Updated by Avan Thakkar almost 4 years ago

  • Related to Bug #46272: mgr/dashboard: workaround needed for ad-hoc filter of the tables added
Actions
Copy link
 #9

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #46312: nautilus: mgr/dashboard: Prometheus query error while filtering values in the metrics of Pools and OSDs added
Actions
Copy link
 #10

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #46313: octopus: mgr/dashboard: Prometheus query error while filtering values in the metrics of Pools and OSDs added
Actions
Copy link
 #11

Updated by Avan Thakkar almost 4 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link
 #12

Updated by Nathan Cutler almost 4 years ago

  • Status changed from Resolved to Pending Backport
Actions
Copy link
 #13

Updated by Nathan Cutler almost 4 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
 #14

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 148 to Monitoring
Actions
Copy link

Also available in: Atom PDF