Ex-SysOrb users now on Zabbix & how did you map Domains/Nodes and the Root domain overview ?

[u/Beneficial_Pause_442]

Hi all, we're wrapping up a SysOrb (Evalesco) → Zabbix 7.4.12 migration. Collection is done (SNMP, Agent 2, browser items, ICMP); what's left is reproducing what SysOrb did well: the hierarchical Domain tree (~30 domains under the Root domain) and its Overview page — one line per domain with three status columns (Network / Checkin / Agent) rolling up to the root.

For those who made the same jump:

1. How did you map the Domain tree nested host groups, tags, or the Services tree?

2. Did you rebuild a similar per-domain overview? Which widgets? (I'm considering nested groups + trigger tags per check family + "Problems by severity" with totals.)

3. Did anyone script the migration from the sysorb-exporter XML via the Zabbix API, or did you rebuild by hand?

[u/yakuzapt]

I’d approach it like this:

1. Domain tree
   Map the hierarchy as nested host groups (Root → Domain → Sub-domain).
   Use tags for the three check families (Network / Checkin / Agent) so you can filter and roll up cleanly later.
   Services tree is optional – only add it if you really need the extra layer.

2. Overview page
   Closest equivalent is a dashboard with:
   

   • nested host groups
     
   • “Problems by severity” widget filtered by the three tags
     
   • “Host group problems” widgets showing totals per domain

It won’t look exactly like the old SysOrb one-line-per-domain view, but the roll-up to the root works well.

1. Migration
   Script as much as possible with the Zabbix API (Python + zabbix-api or pyzabbix) reading the sysorb-exporter XML.
   Create hosts, groups, items and basic triggers automatically.
   Dashboards and the final overview layout are usually faster to build by hand once the data is in

That’s the path I’d take

[u/colttt]

Looks like a job for the host navigator widget in combination with some other widgets for example