<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on ZabFox — Open Source Extensions for Zabbix</title><link>https://www.zabfox.de/en/blog/</link><description>Recent content in Blog on ZabFox — Open Source Extensions for Zabbix</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 29 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.zabfox.de/en/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Network Topology 5.6.0 — reading switches more cleanly: typed LLDP, management IP and a PoE budget alert</title><link>https://www.zabfox.de/en/blog/release-5-6-0/</link><pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/release-5-6-0/</guid><description>The main module and all eight dashboard widgets run on Zabbix 7.0 LTS, 7.4 and 8.0. Get it: github.com/linuser/zabbix-network-topology/releases
The 5.5.27 post ended at the MAC finder and the move to Zabbix 8. A fair amount has landed since — rings, spanning-tree, per-port PoE, the VLAN view, aerial and floor-plan backgrounds, a WLAN widget — and with 5.6.0, three things that make the everyday noticeably calmer. The full list is in the changelog; here are the highlights.</description></item><item><title>Network Topology 5.5.27 — find every device on its port</title><link>https://www.zabfox.de/en/blog/release-5-5-27/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/release-5-5-27/</guid><description>Main module and all five dashboard widgets run on Zabbix 7.0 LTS and 7.4. Grab it here: github.com/linuser/zabbix-network-topology/releases
The 5.5 post stopped at 5.5.2 — faster, nosier, suspicious. Since then it has grown up to 5.5.27: two bigger things and a long clean-up wave. The short version.
The whole module at a glance: the map plus four more dashboard widgets — a KPI ring, the Topology Health Score, an item list and the table.</description></item><item><title>Network Topology 5.5 — faster, nosier, and then we tried to break it</title><link>https://www.zabfox.de/en/blog/release-5-5/</link><pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/release-5-5/</guid><description>Main module and all five dashboard widgets run on Zabbix 7.0 LTS and 7.4. Grab it here: github.com/linuser/zabbix-network-topology/releases
5.5 didn&amp;rsquo;t land in one go — it&amp;rsquo;s really three releases with three different moods. 5.5.0 got fast. 5.5.1 got curious. 5.5.2 got paranoid. Here&amp;rsquo;s the short version of all three.
5.5.0 — three times faster (and we can prove it) A full map of 1000 hosts, 1425 edges and 43 200 items used to take 4681 ms.</description></item><item><title>Network Topology 5.4.0 — every cable gets its own line</title><link>https://www.zabfox.de/en/blog/release-5-4-0/</link><pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/release-5-4-0/</guid><description>This release came out of an issue, and the person who reported it built it himself. Christos Diamantis described what was missing; two days later the pull request was there, with tests that are stricter than mine. It&amp;rsquo;s the first structural change to the module that isn&amp;rsquo;t mine.
Two switches, four cables, one line Up to 5.3 the rule was: one device pair, one edge. If a switch reported the same neighbour a second time on a different port, that report was folded into the edge that already existed.</description></item><item><title>Network Topology 5.3.2 — five reports, five bugs</title><link>https://www.zabfox.de/en/blog/release-5-3-2/</link><pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/release-5-3-2/</guid><description>The last two releases didn&amp;rsquo;t come from a plan, they came from the inbox. Five people described what their map was drawing wrong. Three sent screenshots, two sent SNMP walks that proved their switches were fine and the module wasn&amp;rsquo;t.
A ghost called F8 One map had an unknown node named &amp;ldquo;F8&amp;rdquo; hanging off five switches, with FC, F4 and BC next to it. The answer was sitting in the item names: Aruba switches answer the CDP cache with the neighbour&amp;rsquo;s MAC instead of its name.</description></item><item><title>Network Topology 5.3.0 — edges in detail, filters &amp; GraphML</title><link>https://www.zabfox.de/en/blog/release-5-3-0/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/release-5-3-0/</guid><description>After the 5.1 release things moved quickly — 5.2.0 and now 5.3.0. The map doesn&amp;rsquo;t just look nicer; in large environments it becomes usable at all.
Every link now tells its story Clicking an edge opens a detail panel: both ports, utilisation against the negotiated speed — and errors and discards at the port rather than as a host total. When an interface drops packets you see which one, not just that the host is affected.</description></item><item><title>On video: Quadrata shows Network Topology for Zabbix</title><link>https://www.zabfox.de/en/blog/quadrata-video/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/quadrata-video/</guid><description>Great feedback from the community: Dimitri Bellini, CEO of Quadrata and a regular voice around Zabbix, dedicated a whole video to the module — &amp;ldquo;How to Add Native Network Topology to Zabbix&amp;rdquo;.
How to Add Native Network Topology to Zabbix Clicking loads the video from YouTube (Google). Data (incl. your IP) is transferred to Google — their privacy policy applies. The video covers exactly what the module is built for: installing it natively as a frontend module on Zabbix 7.</description></item><item><title>Network Topology 5.1.0 is here — out of beta</title><link>https://www.zabfox.de/en/blog/release-5-1-0/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/release-5-1-0/</guid><description>Network Topology for Zabbix 5.1.0 is final. After the public beta, the frontend module is now stable — and it picked up its biggest changes since the first release along the way.
Layouts that stick — for everyone Manually drawn links and node positions used to live in the browser. Now they live server-side, in a shared layer and a personal one. So the way you arrange the map is visible to your colleagues too — and it survives a change of browser.</description></item><item><title>Network Topology for Zabbix is now open source — public beta</title><link>https://www.zabfox.de/en/blog/public-beta/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/public-beta/</guid><description>Historical post (July 2026). The module has been stable for a long time — current version 5.5.27. This announcement stays as a record of the time. → Latest posts
Network Topology for Zabbix is now open source — a public beta under AGPL-3.0.
If you run Zabbix, you know the feeling: you can see that a host is red — but not what depends on it. That&amp;rsquo;s exactly what this frontend module is built for.</description></item><item><title>v4.36.0 released</title><link>https://www.zabfox.de/en/blog/v4-36-0/</link><pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/v4-36-0/</guid><description>v4.36.0 is live. A fair bit has happened since the last release post (v4.31) — here are the highlights at a glance.
Ghost nodes (new in v4.36.0) LLDP/CDP neighbours that resolve to no monitored Zabbix host now show up as ghost nodes on the graph — with an edge to the reporting host. They exist on the network but not in monitoring: exactly the gap you want to see. Deliberately drawn &amp;ldquo;unfinished&amp;rdquo; (small, dashed circle, no severity ring, no traffic) and toggled from the toolbar.</description></item><item><title>v4.31.0 released</title><link>https://www.zabfox.de/en/blog/v4-31-0/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/v4-31-0/</guid><description>v4.31.0 is live — among others on zabbix.fox1.de.
This release tightens the shipped bundle: the production bundle is now minified, cutting the gzip transfer from around 103 KB to ~79 KB. The source map only loads when the DevTools are open — so no dead weight in normal operation.
Upgrade Unzip the new release, reload php-fpm — done. Steps in the docs. No breaking changes.</description></item><item><title>From 44 requests to one: esbuild bundling</title><link>https://www.zabfox.de/en/blog/esbuild-bundling/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.zabfox.de/en/blog/esbuild-bundling/</guid><description>Until now the module loaded around 44 separate JavaScript files in the frontend. As of v4.30.0 everything is combined into a single bundle with esbuild.
What that gets you:
One request instead of ~44 — faster loads, fewer roundtrips. CSP-friendly — fits strict content security policies. Real stack traces — thanks to a source map (only with DevTools open) you land in the actual source. No build tool needed on your side: the finished bundle ships in the release.</description></item></channel></rss>