feat(view): tiles and impact #6

Merged
dawid merged 1 commit from tiles-impact into main 2026-11-19 14:47:06 +00:00
Owner

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), with ack / 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); above max aggregations it falls back to the pie like the other views of the trees.

Also:

  • The list's narrowing by a group is now a generic scope (groups, bars, impact).
  • The unit stub can add shared hosts and services (extra_leaves); the screenshot samples share three hosts across aggregations, so the README's other pictures changed slightly.
  • Integration tests for both views on 2.4 and 2.5.

Stacked on #5 (curved labels): merge that first, then this one's diff is only its own commit.

70 unit tests pass locally.

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), with `ack` / `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); above `max` aggregations it falls back to the pie like the other views of the trees. Also: - The list's narrowing by a group is now a generic scope (groups, bars, impact). - The unit stub can add shared hosts and services (`extra_leaves`); the screenshot samples share three hosts across aggregations, so the README's other pictures changed slightly. - Integration tests for both views on 2.4 and 2.5. Stacked on #5 (curved labels): merge that first, then this one's diff is only its own commit. 70 unit tests pass locally.
feat(view): names bent along the rings in the pie and in the rings' wide segments
All checks were successful
CI / unit (pull_request) Successful in 1m29s
CI / integration (Checkmk 2.4) (pull_request) Successful in 5m10s
CI / integration (Checkmk 2.5) (pull_request) Successful in 5m19s
CI / integration (update 2.4 to 2.5) (pull_request) Successful in 7m47s
CI / release (pull_request) Has been skipped
6b483d0487
ECharts writes text only straight. The page draws these names itself, as SVG
text on paths along the arcs, from the layout ECharts computed: the pie's slices
get their state and count, the rings' wide segments their name. Narrow segments
keep theirs straight along the radius. Each reads from left to right.
feat(view): tiles, one hexagon per aggregation, and impact, the hosts and services that drag the most aggregations down
All checks were successful
CI / unit (pull_request) Successful in 1m37s
CI / integration (Checkmk 2.4) (pull_request) Successful in 4m48s
CI / integration (Checkmk 2.5) (pull_request) Successful in 4m59s
CI / release (pull_request) Has been skipped
CI / integration (update 2.4 to 2.5) (pull_request) Successful in 7m39s
ccffcc41df
tiles needs only the states, so it works for any number of aggregations; impact walks
the trees and ranks what is not OK by its aggregations that are not OK, top= rows.
A click on an impact bar narrows the list to that host's or service's aggregations.
dawid merged commit 91b0b419e0 into main 2026-11-19 14:47:06 +00:00
dawid deleted branch tiles-impact 2026-11-19 14:47:06 +00:00

Tests of CI / unit: passed

70 passed, 0 failed, 0 skipped (70 tests, 41.0 s)

Of ccffcc41df, the run, updated by every run.

<!-- ci-report tests: CI-unit --> ### Tests of CI / unit: passed **70 passed, 0 failed, 0 skipped** (70 tests, 41.0 s) <sub>Of ccffcc41df, [the run](https://git.ciepiela.org/dawid/checkmk-bi-charts/actions/runs/11), updated by every run.</sub>

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.

<!-- ci-report tests: CI-integration-Checkmk-2.4- --> ### Tests of CI / integration (Checkmk 2.4): passed **17 passed, 0 failed, 0 skipped** (17 tests, 236.8 s) <sub>Of ccffcc41df, [the run](https://git.ciepiela.org/dawid/checkmk-bi-charts/actions/runs/11), updated by every run.</sub>

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.

<!-- ci-report tests: CI-integration-Checkmk-2.5- --> ### Tests of CI / integration (Checkmk 2.5): passed **17 passed, 0 failed, 0 skipped** (17 tests, 243.3 s) <sub>Of ccffcc41df, [the run](https://git.ciepiela.org/dawid/checkmk-bi-charts/actions/runs/11), updated by every run.</sub>

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.

<!-- ci-report tests: CI-integration-update-2.4-to-2.5- --> ### Tests of CI / integration (update 2.4 to 2.5): passed **6 passed, 0 failed, 0 skipped** (6 tests, 405.3 s) <sub>Of ccffcc41df, [the run](https://git.ciepiela.org/dawid/checkmk-bi-charts/actions/runs/11), updated by every run.</sub>
Sign in to join this conversation.
No description provided.