feat(view): tiles and impact #6
Loading…
Reference in a new issue
No description provided.
Delete branch "tiles-impact"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two more views, as suggested in the chat about chart types.
view=tiles: one hexagon per aggregation, worst first, its name inside (wrapped, at most three lines), withack/downtime. Only the states are needed, no trees, so it works for any number of aggregations. Hover: state and flags; click: the state below the chart.view=impact: one bar per host or service that is not OK, as long as the aggregations it is part of, a segment per state of those. Ranked by how many of its aggregations are not OK, then by how many there are, so a shared core switch or storage comes first. The dot before the name is its own state. Clicking a segment narrows the list to those aggregations.top=sets the rows (default 15); abovemaxaggregations it falls back to the pie like the other views of the trees.Also:
extra_leaves); the screenshot samples share three hosts across aggregations, so the README's other pictures changed slightly.Stacked on #5 (curved labels): merge that first, then this one's diff is only its own commit.
70 unit tests pass locally.
Tests of CI / unit: passed
70 passed, 0 failed, 0 skipped (70 tests, 41.0 s)
Of
ccffcc41df, the run, updated by every run.Tests of CI / integration (Checkmk 2.4): passed
17 passed, 0 failed, 0 skipped (17 tests, 236.8 s)
Of
ccffcc41df, the run, updated by every run.Tests of CI / integration (Checkmk 2.5): passed
17 passed, 0 failed, 0 skipped (17 tests, 243.3 s)
Of
ccffcc41df, the run, updated by every run.Tests of CI / integration (update 2.4 to 2.5): passed
6 passed, 0 failed, 0 skipped (6 tests, 405.3 s)
Of
ccffcc41df, the run, updated by every run.