v0.2.1 the node list reports kind instead of source, detail tabs filtered by kind, kind-shaped Overview, URL/DNS/Meraki badges in the inventory, + adds a node, Edit node on the pane
Latest📋 Full release notes: RELEASE_NOTES.md
Container images published by CI for this release (also tagged :latest, since this version carries no pre-release suffix):
ghcr.io/horryworks/yagra-core:v0.2.1
ghcr.io/horryworks/yagra-poller:v0.2.1
ghcr.io/horryworks/yagra-web:v0.2.1
Breaking changes
- The node list now reports what each node is.
GET /api/v1/nodesand
GET /api/v1/nodes/by-groupreplace the two-valuedsourcefield withkind— the same
meraki/url/dns/devicevalueGET /api/v1/nodes/{id}already returned, resolved by
the one function the scheduler also asks, so a list row can no longer disagree with the detail
page it opens.sourceis removed rather than deprecated: it was a lossy projection added for a
single tree badge, and it would have read"device"for every monitor kind added since and every
one added next. Mapping for API clients:source == "meraki"becomeskind == "meraki", and
everything that was"device"is now one ofdevice,urlordns. The MCPlist_nodesand
get_node_statustools carry the samekind, so an AI client can tell a URL monitor from a
switch before asking which metrics it has.
Improvements
- A node's detail page now shows only the tabs its kind can fill. A URL or DNS monitor shows
Overview and Collection; a Meraki device adds Events. Interfaces, Neighbors and Flow are gone from
those kinds — not because they were empty today, but because they cannot ever be filled: a URL or
DNS monitor is dispatched one HTTP or DNS check and is never SNMP-walked or pinged, and a Meraki
device is polled through the Dashboard API with no per-node job at all. Nothing becomes
unreachable: passive events for any node remain at Alerts ▸ Events filtered by node, and none
of these kinds is ever a NetFlow exporter. A bookmarked link to a tab a node does not show now
lands on Overview and corrects the address bar, instead of drawing a pane with no tab selected. - The Overview of a monitor stops describing a device it is not. A DNS monitor used to lead with
an empty "ICMP RTT · last 30 min" chart and a facts grid whose Maker, Model, SNMP credential and
Uptime were four consecutive em dashes — all of them answers to an SNMP walk that kind never
receives. The chart is now shown only where ICMP is actually sent, the grid lists only rows that
can hold a value (a DNS monitor gains a Resolver row instead), and the line under the node's name
readswg.example.net · Arather than0.0.0.0 · unknown device. Each kind's "last seen" is now
read from the metric it actually produces, so monitors show one at all. - URL, DNS and Meraki nodes are now labelled as such in the inventory. A short
URL/DNS/
Merakibadge sits after the name in the node tree, in a group's member list and beside the title
on the detail page, with the full kind on hover. Ordinary devices stay unmarked, so the badge means
"read this one differently". Previously only Meraki was distinguishable and a URL monitor was
indistinguishable from a switch. - The Collection tab no longer shows a
0count pill on nodes whose profile attaches no
collection sets — which is every URL and DNS monitor. A zero there read as a fault; it now shows
no pill, matching the Interfaces tab's existing rule. - The inventory's + adds a node, not just a group. It now opens a two-item menu — add node, add
group — and both act on whatever the tree has selected: with a group (or a node inside one)
selected they readAdd node to "Tokyo"…/Add subgroup in "Tokyo"…, and with nothing selected
they file at top level. Adding a node used to be reachable only by right-clicking a tree row,
which is undiscoverable on a desktop and impossible on a touch device, wherecontextmenunever
fires — so on a phone the inventory could grow folders but not nodes. The + on a group row offers
the same two, scoped to that group. - The Add node dialog now has a Group field. It is preselected from wherever the dialog was
opened and can be changed before saving, instead of the previous read-only "Adding to top
level" note. This also fixes a node added from a selected group's pane landing at top level
regardless of the group. - "Edit node" is now on the node pane of the Nodes page, not only on the full detail page.
Changing a node's profile, credential, maker/model or poller pool from the inventory split meant
first pressing "Open detail" — a button that reads as navigation, not as editing, so the edit path
was effectively hidden. It sits beside "Move…" and opens the same dialog.
Bug Fixes
- A DNS monitor's resolution history no longer paints its status chip over the next column. The
Resolution column was 140px wide while "No such name (NXDOMAIN)" — and its Japanese equivalent
more so — needs half again as much, and a status chip is deliberately never squeezed, so it
overflowed at every browser width. The column is now sized for the longest label in either locale,
and the chip truncates with an ellipsis (full text on hover) rather than spilling if a future label
or a wider system font still does not fit.