Project

General

Profile

Actions

Bug #42961

closed

osd: increase priority in certain OSD perf counters

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

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
% Done:

0%

Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
BlueStore, OSD
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

There are reports from users missing stats in dashboard/prometheus mgr modules about the following perf counters:

        "bluestore_compressed",
        "bluestore_compressed_allocated",
        "bluestore_compressed_original",

They all are tagged as priority 0 (PRIO_DEBUGONLY), and ceph-mgr filters (by default) out any perf counter below 5 (PRIO_USEFUL). There are 2 possible approaches here:
  • Ad-hoc fix by increasing the priority for these specific perf counters from 0 to 5.
  • Longer term one: by providing a mgr option to cherry-pick perf counters of lower than default priority and export them.

Related issues 2 (1 open1 closed)

Related to mgr - Feature #46212: mgr/prometheus: allow users to export metrics of lower prioritiesIn ProgressErnesto Puerta

Actions
Copied to RADOS - Backport #43245: nautilus: osd: increase priority in certain OSD perf countersResolvedNathan CutlerActions
Actions

Also available in: Atom PDF