-
Type:
Change Request
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 7.4.12
-
Component/s: Frontend (F)
Summary
Add a per-map or per-element option to display problem status/coloring based only on hosts placed directly on that map, without rolling up problem severity from nested submap elements.
Problem
Currently, when a map contains a submap element, that element's color/severity reflects the worst problem anywhere inside the submap hierarchy, including problems many levels deep. On large, heavily-nested topologies this means a top-level overview map can show critical (red) status driven entirely by something several submaps away, with no way to tell at a glance whether the problem belongs to a host on this map or is being inherited from below.
Proposed behavior
- Add a map-level (or map-element-level) setting, e.g. "Problem display scope", with options:
- Include submap problems (current behavior, default preserves backward compatibility)
- This map's hosts only (new submap elements always render at their own "ok" baseline color/icon regardless of what's inside them; only hosts/triggers directly on the map drive its status)
- Setting should be configurable per map, similar to existing "Problem display" (All / Separated / Unacknowledged only) map property, so operators can choose the model per map rather than globally.
Use case
Large ISP/NOC topology with 8,000+ hosts organized into a multi-level map hierarchy (region → site → device). Top-level overview maps are meant to show regional health, not get colored red because of an unrelated single-host problem four submap levels down. Currently the only workaround is manually avoiding submap nesting, which defeats the purpose of hierarchical maps at scale.
Related issues
ZBXNEXT-7529/ZBXNEXT-9626– related but opposite direction: requests more rollup (nested host group problems not currently surfacing). Confirms this is the same underlying "problem visibility scope" design question, just the other polarity.- ZBXNEXT-3260 – also related: requests submap status highlighting to correctly reflect contained problems. This ticket asks for the inverse – the ability to turn that off.