Notifications
Clear all
Topic starter
30/07/2026 10:47 pm
TL;DR: Changing Zabbix map icon label sizes through custom CSS and front-end configuration gives operators a way to improve readability across MIRACLE ZBX versions 5.0, 6.0, and 7.0, but it also introduces maintenance risk when upgrades alter the underlying code paths, according to Cybertrust Japan. The security lesson is that interface customisation must be treated as a governed change, not a harmless visual tweak, because supportability and configuration drift matter in operational monitoring.
NHIMG editorial — based on content published by Cybertrust Japan: changing Zabbix map label sizes with a custom theme
Questions worth separating out
Q: How should teams manage custom monitoring UI changes without creating drift?
A: Treat custom UI changes like any other production configuration.
Q: Why do small dashboard changes create operational risk in practice?
A: Small dashboard changes become risky when teams rely on the interface to make rapid decisions.
Q: What do teams get wrong about customising monitoring platforms?
A: Teams often treat presentation-layer customisation as harmless because it does not change the underlying data.
Practitioner guidance
- Version-control custom CSS overrides Store the theme copy, selector changes, and any font-size rules in source control so the exact display state can be reproduced after a change or outage.
- Test custom themes after every upgrade Run a post-upgrade check on map labels, icon overlays, and user-specific theme settings before returning the monitoring UI to normal use.
- Separate global and user-level display changes Decide whether label sizing is an organisation-wide standard or an individual preference, then apply it consistently through the correct configuration path.
What's in the full article
Cybertrust Japan's full blog post covers the operational detail this post intentionally leaves for the source:
- Exact CSS selector syntax used to enlarge map icon labels in MIRACLE ZBX.
- Step-by-step file copy and edit workflow for creating a custom theme from the default Blue theme.
- Front-end configuration changes needed to register the custom theme in APP.php.
- User-level and global theme selection steps across MIRACLE ZBX 5.0, 6.0, and 7.0.
👉 Read Cybertrust Japan's guide to changing Zabbix map label sizes →
Zabbix map label sizing: what it means for monitoring teams?
Explore further
30/07/2026 10:56 pm
Interface customisation becomes a governance issue the moment operations rely on it for decision-making. The article is about a visual change, but the underlying lesson is that front-end overrides can create hidden dependencies on code paths, theme files, and upgrade timing. That pattern is familiar in identity programmes too, where local exceptions and ad hoc changes become hard to reconcile later. The practitioner conclusion is simple: if the display supports operational response, it deserves change control equal to any other monitored asset.
A question worth separating out:
Q: Who should own front-end customisations in operational systems?
A: Front-end customisations should be owned by the team responsible for the platform lifecycle, not left to ad hoc local edits. Ownership should include testing after upgrades, documented exceptions, and a clear decision on whether the change is a standard setting or a user preference.
👉 Read our full editorial: Zabbix map label sizing changes and what they mean for monitoring
