OrbVis 0.5.0 is out
A bigger one this time. 0.5.0 wraps up three weeks of work on the Folder board, finishes the move onto Checkmk’s design system, and — maybe most importantly — adds a release-test pipeline that actually caught several bugs before you could hit them.
What changed?
The Folder board grew up
The experimental SETUP folder-tree board from 0.4.1 got a full iteration based on early feedback:
- It now opens in the treemap view — the glanceable status surface. Row details moved to hover, bulk acknowledge/downtime to right-click, and the list view stays one click away.
- Built for big sites: live updates now stream as per-tick SSE deltas instead of full-tree pushes, the list is virtualized and map tiles are pixel-culled.
- Server-side service search (
s: prefix) that scales to millions of services, search auto-expands to reveal matches, and the problems-only filter has a Problem severity threshold — on a typical site almost every host carries some WARNING service, so you can narrow to critical/down only.
- Per-board site scoping with a site picker for distributed setups.
Distributed monitoring: per-site trust
When a remote site stops responding, its hosts no longer flap to UNKNOWN. They freeze at their last known state, marked as stale, with a visible warning — so a dead replication link doesn’t paint half your board red for the wrong reason.
Lines, icons, visibility
- NagVis bent lines import faithfully now (explicit middle point), with a Remove bend context action.
- Per-line z-layering plus a board-wide
default_z, matching NagVis semantics on import.
- Weathermap lines accept a second (outbound) metric.
- Custom icons are tinted by object status with a solid ring, and the show only problems toggle is available on every board type.
Checkmk look & feel, completed
The frontend now runs fully on Checkmk’s design system: Tailwind is gone in favor of scoped CSS on cmk tokens, the vendored cmk-frontend-vue tree tracks current master, and i18n moved to vue3-gettext following cmk conventions. If you run OrbVis next to Checkmk, it should feel native — including the status color palette, which now also applies to standalone deployments.
Permissions tightened
Host/service actions are gated on granular Checkmk command permissions instead of a blanket admin check, board create/configuration follows orbvis.edit_all/configure, and BI aggregation titles/trees are scoped to the requesting user’s contact visibility.
One thing worth highlighting
This release got a much harder test pipeline: every release now runs a real upgrade test from the previous release tag (old data written by the old version, read by the new one), plus an input sweep that mutates every rendered control on every settings surface. That pipeline caught — and 0.5.0 fixes — among others:
omd restart could kill the OrbVis service when a graceful shutdown hung (the old process kept the port, the new one crashed on bind). The init script now escalates properly and caps graceful shutdown.
- A vendor-refresh regression that silently broke every toggle switch and the settings section navigation.
- Healthy BI aggregations rendering as PENDING under specific conditions.
Full list in the changelog.
How to update?
Same as before — upload the new MKP via Setup → Extension Packages or on the CLI:
OMD[SITENAME]:~$ orbvis-setup uninstall && mkp disable orbvis && mkp remove orbvis && mkp add /tmp/orbvis-cmk-2.X.mkp && mkp enable orbvis && orbvis-setup
Your boards, backgrounds and settings are kept. (And since 0.3.0, a plain omd restart after mkp enable does the setup step on its own.)
Where can I find it?
As always: feedback, bug reports and ideas are very welcome — here in the thread or on GitHub.