Project

General

Profile

Cleanup #46898

Feature #40907: mgr/dashboard: REST API improvements

mgr/dashboard/api: move/create OSD histogram in separate endpoint

Added by Ernesto Puerta about 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Low
Category:
General - Back-end
Target version:
% Done:

100%

Tags:
Backport:
octopus
Reviewed:
Affected Versions:
Pull request ID:

Description

As a result of https://tracker.ceph.com/issues/26954, the OSD histogram information will be removed from the api/osd/ endpoint. As a side effect, we found out that this histogram was retrieved via send_command API, which is not recommended for endpoints that are polled often (like the OSD, which is invoked every 5 secs x number of OSDs.

If we deem this histogram information valuable for end users (it seems rather developer focused), the suggestion would be to restore this information to a separate endpoint, like api/osd/{id}/histogram.


Related issues

Follows Dashboard - Feature #26954: mgr/dashboard: Remove Histogram component Resolved
Copied to Dashboard - Backport #47607: octopus: mgr/dashboard/api: move/create OSD histogram in separate endpoint Resolved

History

#1 Updated by Ernesto Puerta about 2 years ago

  • Follows Feature #26954: mgr/dashboard: Remove Histogram component added

#2 Updated by Alfonso Martínez about 2 years ago

  • Parent task set to #40907

#3 Updated by Aashish Sharma about 2 years ago

  • Assignee set to Aashish Sharma

#4 Updated by Aashish Sharma about 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 37192

#5 Updated by Lenz Grimmer about 2 years ago

  • Status changed from Fix Under Review to Pending Backport

#6 Updated by Nathan Cutler about 2 years ago

  • Copied to Backport #47607: octopus: mgr/dashboard/api: move/create OSD histogram in separate endpoint added

#7 Updated by Alfonso Martínez almost 2 years ago

  • % Done changed from 0 to 100

#8 Updated by Nathan Cutler almost 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".

#9 Updated by Ernesto Puerta over 1 year ago

  • Project changed from mgr to Dashboard
  • Category changed from 146 to General - Back-end

Also available in: Atom PDF