INTEGRATION / ZABBIX
Zabbix triggers in, one incident out
When a database falls over, Zabbix can fire a dozen triggers in a minute. Incident Lake opens one incident, links the related triggers to it, and runs the response in your Slack or Teams thread so nobody spends the first ten minutes de-duplicating alerts.
1
Trigger fires
e.g. Zabbix: DB connection errors PROBLEM
2
Opened and grouped
Related triggers attached to one incident, posted to Slack or Teams
3
People decide
Commander and severity confirmed one at a time; recovery times recorded
Illustrative mock. Demo video coming soon.
What it does
- Opens incidents from Zabbix triggers
- Links multiple triggers to a single incident
- Lets the agent read Zabbix problem data (read-only)
- Detects detection, mitigation and resolution times; watches for recurrence
- Feeds the postmortem draft
What it does not do
- Change Zabbix configuration or triggers
- Set severity or close incidents on its own
- Page your on-call engineer
Setup at a glance
Add the Zabbix integration
Register connection details in integration settings. Secrets are encrypted per tenant.
Pick a channel
Choose the Slack or Teams channel where new incidents should land.
Fire a test trigger
Confirm the incident opens and posts. We share detailed steps during onboarding.
FAQ
Does Incident Lake write to Zabbix?
No. The Zabbix connection is read-only.
Our Zabbix is on an isolated network. Can we still use it?
The Self-Hosted edition runs inside your environment with a self-hosted LLM. Talk to us about the setup.
Does it work in Microsoft Teams?
Yes, Slack and Teams are both first-class.
Connect Zabbix and try it free
Work email and company name. That's the whole form.
Connect Zabbix free →