ITOC360 at Zabbix Summit 2026
Our team will be at Zabbix Summit 2026, joining the global Zabbix community in Riga this October. Let's talk about turning monitoring alerts into clean, actionable incidents.
Why we are going?
Zabbix answers the question what broke. It answers it thoroughly, at a scale few commercial tools match.
The question it deliberately leaves open is who now. Who is on shift at 3 a.m. Who gets called when that person does not answer. What happens when one failed hypervisor produces sixty events and every one of them is delivered to everybody.
That gap is where ITOC360 works. We take Zabbix problems and turn them into managed incidents: correlated into one item instead of sixty, routed by tag to the team that owns the service, escalated automatically when nobody acknowledges, and resolved when Zabbix clears the problem.
What we want to talk about in Riga?
We are bringing questions more than a pitch. Three in particular:
How are you routing today?
Most teams we meet started with a webhook and a shared mailbox, then bolted on scripts. We would like to know what you built, what broke, and what you gave up on.
How do MSPs handle multi-tenancy?
If you run Zabbix as a service — proxies across customer sites, different escalation rules and response commitments per customer — the on-call problem is a different problem. This is the case we have built around, and the one we most want to pressure-test against people doing it in production.
What does noise actually cost you?
Everybody agrees alert fatigue is bad. Very few teams have a number for it. If you have one, we would like to hear how you measured it.
Who we would like to meet?
MSPs and integrators delivering monitoring as a service, NOC teams covering multiple sites or customers, and enterprise IT operations teams running Zabbix alongside other tooling.
