ilert Documentation
WebsiteAPI ReferenceLoginStart for Free
  • Getting Started
    • Core concepts
    • FAQ
      • Renaming of Incidents to Alerts
    • Import from PagerDuty
    • Import from StatusPage.io
  • Alerting
    • Dashboard
    • Alert sources
    • Notification settings
      • Mute notifications
    • Support hours
    • Maintenance windows
    • Heartbeat monitoring
      • Prometheus Heartbeat Example
      • CLI Heartbeat Examples
    • Deployment events
    • 🏛️Understanding event flows
    • ilert sender IDs, domains and IPs
      • SMS and voice alerts in China
  • On-call management & Escalations
    • Escalation policies
    • On-call schedules
      • My on-call shifts
      • Recurring schedules
      • Static schedules
    • Coverage requests
  • ChatOps
    • Overview
    • Integration for Slack
      • Receive and respond to alerts in Slack
      • Create a dedicated Slack channel for an existing alert
      • Create alerts in Slack
      • Look up who is on-call
    • Microsoft Teams Integration
      • Microsoft Teams Chat Integration
        • Microsoft Teams Integration via Incoming Webhook
        • Microsoft Teams Integration via Workflows
      • Microsoft Teams Meeting Integration
      • Create a channel for an existing alert in Microsoft Teams
      • Create alerts in Microsoft Teams
      • Look up who is on-call in Microsoft Teams
  • Incident comms & status pages
    • Getting started
    • Services
    • Incidents
    • Status pages
      • Public vs private status pages
      • Audience-specific status page
    • Metrics
      • Import metrics from Datadog
      • Import metrics from Prometheus
  • 🪄ilert AI
    • Introduction
    • Using ilert AI for efficient incident communication
    • Using ilert AI for post-mortem creation
    • Using ilert AI for schedule generation
    • Using ilert AI for alert grouping
    • Global Search enhanced by ilert AI
      • Bulk resolving similar alerts
  • Call Routing
    • Getting started with call routing
    • Routing calls using call flows
    • Call routing (legacy)
      • Routing calls based on support hours
      • Voicemail only mode
      • Managing call routing alerts
      • Adding webhooks and outbound chat messages
      • Uploading custom audio responses
  • User Administration
    • User roles and permissions
    • Team-based organisation
    • Single sign on
      • Setting up SSO with GSuite
      • Setting up SSO with Microsoft Azure Active Directory
      • Setting up SSO with Okta
      • Setting up SSO with Auth0
      • Auto provisioning users & teams
    • 🔐Two-factor authentication / MFA
  • Reports
    • Overview
    • Alerts
  • Mobile App
    • Getting started with ilert mobile app
    • Mobile app notification settings
    • Critical push notifications and DND overrides
      • iOS critical alerts configuration
      • Android Push Notification DND Configuration
    • On-call widget
  • INTEGRATIONS
    • Types of integrations
    • Inbound integrations
      • 4me Integration
      • Ansible Automation Platform AWX Integration
      • Amazon CloudWatch Integration
      • Amazon SNS Integration
        • Amazon SNS Inbound Integration
        • Amazon SNS Outbound via AWS Lambda
      • Azure Alerts Integration
        • Azure Activity Logs
        • Azure Metric
        • Azure Logs
        • Azure Service Health
        • Azure Sentinel
        • Budget Alert
      • Apica Integration
      • AppDynamics Integration
      • AppSignal Integration
      • AWS Budgets Integration
      • AWS Cloudtrail Integration
      • AWS DevOps Guru Integration
      • AWS GuardDuty Integration
      • AWS Personal Health Dashboard Integration
      • AWS Security Hub Integration
      • Autotask Inbound Integration
      • Auvik Integration
      • Catchpoint Integration
      • Checkly Integration
      • Checkmk Integration
        • Checkmk Integration (v 1.x)
        • Checkmk Integration (v 2.0+ )
      • Cisco Meraki Integration
      • Cisco ThousandEyes Integration
      • Cisco Webex
      • Cloudflare Integration
      • ClusterControl Integration
      • Connectwise Manage Integration
      • Cortex Integration
      • Cortex XSOAR (formerly Demisto) Integration
      • CrowdStrike Integration
      • Dash0 Integration
      • Datadog Integration
      • Dynatrace Integration
      • Elastic Watcher Integration
      • Email Inbound Integration
        • Email Key Extraction and Resolve Examples
        • Automatically resolve Alerts with Emails
        • Migrating legacy email settings
      • FreshService Integration
      • Gatus Integration
      • GitHub Integration
        • GitHub Advanced Security Integration
        • GitHub Inbound Check Run (Actions) Integration
        • GitHub Inbound Issue Integration
        • GitHub advanced settings
      • GitLab Integration
      • Google Cloud Monitoring (formerly Stackdriver) Integration
      • Google Security Command Center
      • Grafana Integration Overview
        • Grafana Integration
        • Grafana Integration (v 9.x)
      • Graylog Integration
      • HaloITSM Integration
      • HaloPSA Integration
      • HashiCorp Consul
      • Healthchecks.io Integration
      • HetrixTools Integration
      • Honeybadger Integration
      • Honeycomb Integration
      • Hyperping Integration
      • CrowdStrike Falcon LogScale Integration
      • IBM Cloud Functions Integration
      • Icinga Integration
      • InfluxDB Integration
      • Instana Integration
      • IT-Conductor Integration
      • IXON Cloud Integration
      • Jira Inbound Integration
      • JumpCloud Integration
      • Kafka Integration
      • Kapacitor Integration
      • Kentix AlarmManager
      • Keep Integration
      • Kibana Integration
      • Kubernetes Integration
      • LibreNMS Integration
      • Lightstep Integration
      • Loki integration
      • Mezmo Integration
      • Microsoft SCOM
      • Mimir Integration
      • MongoDB Atlas Integration
      • MXToolBox Integration
      • MQTT Integration
      • Nagios Integration
      • N-central Integration
      • Netdata Integration
      • New Relic Integration
        • New Relic Integration (deprecated)
        • New Relic Workflow Integration
      • Oh Dear Integration
      • PandoraFMS Integration
      • Panther Integration
      • Particle Integration
      • Pingdom Integration
      • PostHog Integration
      • Postman Monitors Integration
      • Prometheus Integration
      • PRTG Network Monitor Integration
      • Prisma Cloud Integration
      • Push Notifications
      • RapidSpike Integration
      • Raygun Integration
      • Rollbar Integration
      • Salesforce Integration
      • Samsara Integration
      • Search Guard Integration
      • Sematext Integration
      • Sensu Integration
      • Sentry Integration
      • Server Density Integration
      • ServerGuard24 Integration
      • ServiceNow Inbound Integration
      • SignalFx Integration
      • Site24x7 Integration
      • SMS Integration
      • SolarWinds Integration
      • Splunk Integration
      • StatusCake Integration
      • StatusHub Integration
      • StatusPage Integration
      • Sumo Logic Integration
      • Sysdig Integration
      • TOPdesk Inbound Integration
      • TeamCity integration
      • Terraform Cloud / Terraform Enterprise
      • Tulip Integration
      • Twilio Alarms Integration
      • Twilio Errors Integration
      • Ubidots Integration
      • Uptime Kuma Integration
      • UptimeRobot Integration
      • VictoriaMetrics Integration
      • Zabbix Integration
        • Zabbix 4.4+ Integration
        • Zabbix 2.2 – 4.3 Integration
      • Zammad Inbound Integration
      • Zapier Inbound Integration
      • Zendesk Inbound Integration
    • Outbound integrations
      • Autotask Outbound Integration
      • DingTalk Integration
      • Discord Integration
      • Email Outbound Integration
      • Jira Outbound Integration
      • GitHub Outbound Issue Integration
      • Mattermost Integration
      • ServiceNow Outbound Integration
      • Telegram Integration
      • TOPdesk Outbound Integration
      • Webhook Integration
      • Zammad Outbound Integration
      • Zapier Outbound Integration
      • Zendesk Outbound Integration
      • Zoom Integration
        • Zoom Chat Integration
        • Zoom Meeting Integration
    • Deployment integrations
      • API deployment pipeline
      • Argo CD deployment pipeline
      • Github deployment pipeline
      • GitLab deployment pipeline
  • API
    • API Reference
    • API Version History
      • API user preference migration 2023
      • Discontinuation of Uptime Monitoring
    • Rate Limiting
    • Client Libraries
      • ilert Agent - ilagent
      • Go Client
      • Rust Client
      • Javascript / Node.js Client
    • Terraform
      • Importing ilert UI resources into Terraform state
    • 👩‍💻ICL - ilert condition language
    • ➿ITL - ilert template language
    • API endpoints / samples
      • Creating alerts through events
      • Importing public status page subscribers
    • 🔥Developing ilert Apps
      • Get started with ilert Apps
      • Understanding OAuth2
      • Developing a Backend App with OAuth2
      • Developing a web or native App with OAuth2 and PKCE
      • Token lifetimes, error codes, app verification, etc.
  • Contact us
  • ilert Release Notes
Powered by GitBook
LogoLogo

Product

  • Alerting & Notification
  • On-call Management & Escalations
  • Call Routing
  • Status Pages

Resources

  • Blog
  • Case Studies
  • Security
  • API Reference

Legal

  • Privacy policy
  • Imprint

Increase Your Uptime

  • Start for Free
  • Get a Demo

(c) 2011 - 2025 ilert GmbH

On this page
  • System Requirements
  • In ilert: Create a Zabbix alert source
  • In Zabbix
  • Create ilert user and group
  • Create an alert action
  • Optional: Mapping Zabbix problem severity to alert priority
  • Optional: Bidirectional sync (acknowledges alerts in Zabbix)
  • FAQ
  • Further References

Was this helpful?

Edit on GitHub
  1. INTEGRATIONS
  2. Inbound integrations
  3. Zabbix Integration

Zabbix 4.4+ Integration

The ilert Zabbix Integration helps you to easily connect ilert with Zabbix.

PreviousZabbix IntegrationNextZabbix 2.2 – 4.3 Integration

Last updated 1 year ago

Was this helpful?

System Requirements

Are you using Zabbix 4.3 or lower? Please refer to our guide.

  • Zabbix 4.4+

In ilert: Create a Zabbix alert source

  1. Go to Alert sources --> Alert sources and click on Create new alert source

  2. Search for Zabbix in the search field, click on the Zabbix tile and click on Next.

  3. Give your alert source a name, optionally assign teams and click Next.

  4. Select an escalation policy by creating a new one or assigning an existing one.

  5. Select you preference and click Continue setup. You may click Do not group alerts for now and change it later.

  6. The next page show additional settings such as customer alert templates or notification prioritiy. Click on Finish setup for now.

  7. On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.

In Zabbix

Import ilert media type (optional as of Zabbix 5.0.4)

Are you using Zabbix 5.0.4 or higher? You can skip this section, if you're using Zabbix 5.0.4+, because as of Zabbix 5.0.4, the ilert media type is included in the distribution Zabbix.

1. Download the ilert Zabbix Media Type file from the Zabbix repository

curl -o media_ilert.xml \
   https://raw.githubusercontent.com/iLert/ilert-zabbix/master/media_ilert.xml

2. Go to the Administration → Media types tab and click the Import button.

3. Select import file media_ilert.xml and click the Import button at the bottom to import the ilert media type.

4. Optional: Go to Media types and open the imported iLert media type. You can overwrite the default alert summary with a custom template using the .ILERT.INCIDENT.SUMMARY variable e.g. {TRIGGER.NAME}: {TRIGGER.STATUS} for {HOST.HOST}

5. Click on the Update button to save the media type.

Create ilert user and group

1. Go to the Administration → User groups tab and click on the Create user group button.

2. Set the name for the ilert group (eg. "ilert group").

4. Click the Add button to save the group.

5. Switch to the Users tab and click on the Create user button.

6. Assign an alias and name and add the user to the ilert group. No further details such as a password are required as this user will not log in to Zabbix.

7. Switch to the Media tab and click on the Add link

8. In the media window, select ilert as Type

9. In the Send to field enter the alert source api key that you generated in ilert

10. Click the Add button

11. Click the Add button in the Users tab to save the user.

Create an alert action

1. Switch to the Configuration → Actions tab and click the Create action button

2. Give the action a name, eg "ilert notifications".

3. Perform the following actions on the Operations, Recovery operations and Acknowledgment operations tabs

4. Change the default subject and default message if you want.

5. Click on the New link under Operations and select the iLert group created above under Send to User groups.

6. Click the Add button to save the action

Optional: Mapping Zabbix problem severity to alert priority

ilert supports a mapping configuration for your Zabbix alert source that allows you to map the standard Zabbix severities to ilert priorities. Just enable the checkbox for Priority mapping under Zabbix settings.

Optional: Bidirectional sync (acknowledges alerts in Zabbix)

As the Zabbix API allows for problems to be acknowledged, ilert offers a setting to configure your Zabbix alert source in bidirectional mode. This will automatically create a connector and alert action for your alert source that will pipe accept events from ilert to Zabbix and acknowledge the problem related to the ilert alert.

Enable the Bidirectional checkbox during your alert sources creation. The Url and Api key will show up under Zabbix settings, please provide both and create your alert source. You will see that a connector and alert action have been setup automatically for your alert source.

You cannot add bidirectional mode after an alert source has already been created. You will have to create a new alert source. Bidirectional mode cannot be enabled through the API.

FAQ

Are alerts automatically resolved in ilert?

Yes, as soon as the status of an alert is OK in Zabbix, the associated alert will be resolved in ilert.

Can I link Zabbix to multiple alert sources in ilert?

Yes, create several ilert users in Zabbix and store the corresponding API key in the user Send To field.

What if my internet connection is lost? Are the events generated in Zabbix lost?

No events are lost. The zabbix server tries to send the events to ilert every 30 seconds with 10 attempts (can be configured in media type settings). As soon as your connection is available again, all events are sent to ilert. We also recommend that you monitor your Internet connection with an external monitoring service. You can then send these alerts to ilert too.

While testing the media type I am receiving "Invalid API key" responses, why?

When testing the media type, you will need to provide the ilert alert source API key again and replace the '.ILERT.ALERT.SOURCE.KEY' field, as it is not filled automatically by Zabbix.

The plugin does not work. How do I find the issue?

Will problems in Zabbix be acknowledged if I accept the alert in ilert?

Zabbix links in ilert alerts are invalid, what's wrong?

This is probably because the URL of your Zabbix interface is not configured in the media type settings. Go Administration --> Media types and open ilert. In the Parameters sections, make sure that the value for ZABBIX.URL is correct. Example:

Further References

This blog post in the Zabbix blog outlines how to use Zabbix and ilert with multiple on-call teams, where each team is responsible for a set of host groups in Zabbix, and therefore, will only receive alerts for the services it is responsible for:

3. Switch to the Permissions tab and select the host groups that the ilert group should have read access to, for sending notifications. Without read access, ilert cannot receive notifications for the hosts in the group (see also ).

Please look at the Problems View in Zabbix under the actions column first. If you can not find the error, please contact our support at .

If you have enabled the bidirectional setup during your alet source creation in ilert, yes. See .

here
support@ilert.com
Bidectional sync
Working with multiple on-call teams using Zabbix and ilert
Zabbix 2.2 - 4.3 Integration
Alert grouping