Feature #50980

Feature #47072: mgr/dashboard: Usability Improvements

Cleanup #47073: mgr/dashboard: landing page

mgr/dashboard: advanced cluster visualization

Added by Ernesto Puerta about 1 year ago. Updated 3 months ago.

Component - Landing Page
Target version:
% Done:


Affected Versions:
Pull request ID:



The goal of this feature would be to provide a visual representation of the cluster status covering the following aspects:
  • Data integrity:
    • Goal: Highlight damaged or compromised sections of the cluster. It should help relate how a failure in one cluster item (PG, OSD, host, etc) relates to degraded status in other items (e.g.: a failure in one OSD causes its PGs to become degraded and hence peer PGs in other OSDs will become affected).
    • What: The suitable entity/es for this could be hosts, OSDs, or PGs (data placement items).
    • How: A representation that could fit this goal for this would be ring-like (e.g.: Cassandra OpsCenter) or it could also be a multi-level ring/pie aka Sunburst chart (inner ring for hosts, middle ring for OSDs belonging to that host, and outer ring for PGs belonging to that OSD).
    • Sample scenario: "a given OSD 123 goes down (due to an I/O disk error), then: the OSD 123 stripe in the OSD ring turns red, the inner ring (host) turns orange (warning), and the outer ring (PGs) turn orange (warning). Additionally, the PG replicas in other OSDs would also turn orange (since they are degraded: a replica for each PG is lost).
    • The position of adjacent hosts/OSDs/PGs in the ring may follow some topological criteria (even allowing for more inner rings: hosts belonging to same rack, chassis, row, ... datacenter, etc.)
  • Data movement:
    • Goal: visualize how data moves within the cluster and identify hot-spots and bottlenecks (replica writes, erasure-code chunks read/writes). Client traffic (inbound-outbound) could be optionally left out (client traffic will mostly trigger cluster traffic).
    • What: it's not realistic to display every byte/request traversing the cluster network, so a threshold should be applied
    • How: A representation suitable for this could be the Chord diagram which allows to map flows among segments/stripes in a ring (also in multi-level one). In Chord diagrams the color and width of the segments can be used to describe
  • Data placement:
    • Goal: detect hot-stops and imbalances in data distribution.
    • Is this really an issue after PG balancer module?


Sage suggested using advanced visualization tools for displaying the cluster-OSD recovery I/O:

More references or examples of cluster visualization:


#1 Updated by Ernesto Puerta about 1 year ago

  • Description updated (diff)

#2 Updated by Ernesto Puerta about 1 year ago

  • Description updated (diff)

#3 Updated by Ernesto Puerta 12 months ago

  • Category changed from UI to Component - Landing Page
  • Status changed from New to Triaged

#4 Updated by Ernesto Puerta 4 months ago

  • Tracker changed from Bug to Feature
  • Description updated (diff)
  • Status changed from Triaged to New
  • Assignee deleted (Nizamudeen A)

#5 Updated by Ernesto Puerta 4 months ago

  • Description updated (diff)

#6 Updated by Ernesto Puerta 4 months ago

  • Description updated (diff)

#7 Updated by Ernesto Puerta 4 months ago

  • Tags set to GSoC22
  • Tags set to g

#8 Updated by Ernesto Puerta 3 months ago

  • Description updated (diff)
  • Tags deleted (g)

Also available in: Atom PDF