Zabbix Support
Last reviewed by Tyler Eastridge
AceMQ provides independent 24/7 Zabbix support for server, proxy, database and high-availability estates: an AceMQ engineer and a partner Zabbix specialist on a live bridge for a P1 (response targets from 15 minutes, by plan), a written root-cause analysis after each one, and upgrade planning against the Zabbix life cycle. Zabbix sells its own support tiers; an AceMQ contract complements or replaces them for the operational work, but it does not include access to Zabbix development. AceMQ ships no Zabbix builds.
Support quotes answered within 1 hour, by a senior engineer.
Planning a build, upgrade or migration instead? See AceMQ Zabbix consulting and services.
Customers
Partners
Incident Triage
Common symptoms in Zabbix production environments, and the first thing an engineer checks when one comes in.
| Symptom you're seeing | What we check first | Typical resolution |
|---|---|---|
| Items are delayed and the queue keeps growing | Which items are delayed and which poller type serves them, then process utilization against the 75 percent line in the Zabbix server health template. A few unreachable devices can hold pollers busy and delay everything behind them. | Poller counts and timeouts, unreachable-host handling, or a proxy closer to the devices |
| History cache fills and values are written late | History cache usage against the template's 75 percent alert, then history syncer utilization and write latency on the database. A full history cache means the database cannot absorb writes as fast as the pollers produce them. | Database I/O and indexes, then HistoryCacheSize and syncer count |
| The value cache is in low-memory mode | Value cache usage against its 95 percent alert and the items that read history: triggers with long time windows, calculated items and dashboards. The template raises a High severity alert when low-memory mode is on. | ValueCacheSize against what triggers actually read, or shorter trigger windows |
| The database is busy and the housekeeper never finishes | Housekeeper utilization, retention for history and trends against table size, and whether per-item storage periods or the global override apply. With TimescaleDB, the housekeeper will not drop outdated partitions unless the override options are on. | Retention and override settings, partitioning, or TimescaleDB compression where the license allows it |
| The server will not start, or the schema upgrade is still running after an upgrade | The server log for the database version it found, and whether the schema upgrade is still running. Zabbix warns that the upgrade may take a long time depending on database size. On MySQL and MariaDB with binary logging, a 6.0 upgrade needs superuser privileges or log_bin_trust_function_creators = 1. | Let the upgrade finish, fix the privilege or database version floor, or restore from backup on a planned window |
| A proxy stopped sending data after the server was upgraded | The proxy version against the server's. Zabbix supports proxies of the same major version fully and proxies no older than the previous LTS with limited functionality; anything older or newer is ignored with a warning. SQLite proxies also lose stored history if their database file is older than the new version requires. | Upgrade the proxy to a supported version, and plan SQLite proxy history loss in advance |
| After a failover the frontend shows the wrong node or HA nodes flap | HANodeName and NodeAddress on each node, the failover delay (one minute by default, 10 seconds to 15 minutes allowed) and database replication health. Standby nodes watch the active node's heartbeat and take over when it goes stale. | Node names and addresses, failover delay, or the replication problem behind the flapping |
| Alerts storm, duplicate or arrive without context | The problem and event history for the trigger, trigger dependencies, action conditions and the media type log. A single failed switch pages for every host behind it when no dependency is set. | Trigger dependencies, action conditions and escalation, then maintenance periods |
Typical resolution describes the usual fix for each symptom. Every P1 closes with a written root-cause analysis.
What's Included
No add-on pricing for incidents. No per-ticket charges. One contract covers the whole surface.
Queue growing, history not being written, the server down or a failover that did not go to plan. With response targets from 15 minutes, by plan, an AceMQ engineer and a partner Zabbix specialist join a live bridge, 24/7, to diagnose, not to acknowledge a ticket.
Every P1 closes with a written RCA: what failed, why, the fix applied and the setting or template change that prevents a repeat. Delivered as standard, not on request.
Where each of your servers and proxies sits against the Zabbix life cycle, and the path to the LTS you should run, rehearsed on a copy. The detailed upgrade work is on the Zabbix consulting page.
History and trends growth against retention, housekeeper behavior, partitioning or TimescaleDB, and backup and restore tested against your recovery target.
Poller and syncer utilization, cache sizes and the queue read from Zabbix's own internal metrics, so a change is made for a measured reason.
Proxy versions against the compatibility rule, HA node configuration, TLS and encryption between components, and user and API token hygiene in the frontend.
Why AceMQ
Tickets go to senior engineers briefed on your proxy layout, database and templates, so a P1 call starts with a hypothesis rather than an interview. The proposal states who does the work.
You reach a senior engineer directly by phone, email or Slack. No queue collecting details to relay, and no approval between you and someone who can read a Zabbix server log and act.
AceMQ is not Zabbix and has no access to Zabbix development. Bugs that need a code fix go to Zabbix through your own channel or subscription. What we do is run, tune, upgrade and troubleshoot your estate.
Internal metrics, logs and queue data first, then a change with a rollback point. No setting is changed to see what happens in production.
AceMQ staffs 24/7 across the Americas, EMEA and APAC, so your 3am alert reaches someone in working hours.
Zabbix rarely runs alone. One AceMQ contract and SLA can also cover Prometheus, Grafana, the database underneath and the platforms you monitor, with multi-technology discounts.
Cloud, Kubernetes, bare metal, hybrid, and air-gapped — including environments where you can't give us outbound network access.
Version coverage
Zabbix sets the status of each release. AceMQ supports the lines below 24/7 and plans which version you should be on and when. Fixes for them come from Zabbix.
| Zabbix line | Zabbix support status | AceMQ coverage |
|---|---|---|
| Zabbix 8.0 LTS | Planned by Zabbix for Q4 2026; not released as of 4 Nov 2026 | Upgrade planning now; no support claimed until it ships |
| Zabbix 7.4 | Released 1 Jul 2025; full support until 8.0 LTS arrives, limited support to Q1 2027 | 24/7 support |
| Zabbix 7.0 LTS | Full support to 30 Jun 2027, limited support to 30 Jun 2029 | 24/7 support |
| Zabbix 6.0 LTS | Full support ended 28 Feb 2025; limited support (critical fixes only) to 28 Feb 2027 | 24/7 support, with an upgrade plan |
| Zabbix 7.2, 6.4 and older | Listed as unsupported in the Zabbix documentation | 24/7 support, with an upgrade plan; 5.x and older scoped case by case |
Source: Zabbix life cycle and release policy page and the Zabbix documentation version list, read on zabbix.com on 4 November 2026. Zabbix describes an LTS release as three years of full support plus two years of limited support. The planned 8.0 LTS date is Zabbix's, not AceMQ's, and can move.
How other open-source monitoring options are supported: Prometheus support options.
Who stands behind Zabbix
Zabbix is open source and its maker sells subscriptions. A page that blurs the two sends buyers to the wrong decision, so this one is plain about who does what.
Engineers who run, troubleshoot and upgrade Zabbix, on-call response, root-cause analysis, version planning and performance diagnosis, under one AceMQ contract and SLA.
The releases and the product team. Fixes come from Zabbix, and AceMQ does not fork or rebuild it. Anything that needs the developers goes to Zabbix, so keep a subscription for that if your risk calls for it.
Zabbix supports 6.0 with critical fixes only until 28 February 2027. We map the upgrade path and the outage window, and keep the server healthy until you move.
Upgrades to 7.0 or the next LTS, database work and moves to Prometheus and Grafana are consulting work, scoped and quoted on the Zabbix consulting page, with support in place meanwhile.
Teams that need changes in Zabbix itself or a commercial Zabbix subscription should buy that from Zabbix. A small single-server install with no on-call duty may not need 24/7 cover.
Escalation Path
Every tier reaches a senior Zabbix engineer. There is no tier-1 triage layer to get through.
Response targets by plan; your contract sets the tier.
P1 escalation path
A replay of one P1, from the first page to the written root-cause analysis
Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.
P1 opened, on-call engineer paged
Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.
Senior engineer on your bridge
A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.
Specialists across the stack join
When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.
Written root-cause analysis
Root cause, the fix applied and the prevention steps, delivered after every P1.
Pricing
AceMQ Zabbix support contracts typically run $24,000–72,000 a year, depending on SLA level, scope (number of clusters or nodes, and environments) and deployment (on-premises, virtualized, Kubernetes or cloud-hosted).
| What moves the price | How it changes the contract |
|---|---|
| SLA level | Business-hours cover costs less than 24/7 cover with response targets from 15 minutes, by plan. |
| Scope | More clusters or nodes, and more environments, make a larger contract. |
| Deployment | Self-managed, cloud-managed and Kubernetes estates need different amounts of hands-on work. |
Covering several technologies under one contract, for example RabbitMQ, Kafka and Redis, earns an aggressive discount.
Typical engagements
Typical engagement scenarios: what the work covers and what it delivers. They describe the service, not past results.
Infrastructure Operations Team
A typical engagement for a monitoring team whose busy Zabbix server writes late: a written review of history and trends growth, housekeeper settings, caches and poller capacity, ranked by production risk.
PostgreSQLTimescaleDB
Linux
Global Aviation Technology Provider
Troubleshooting cluster failover, partition handling, and quorum queue issues in a high-stakes aviation operational environment.
RabbitMQ
KubernetesQuorum Queues
Prometheus
GrafanaGlobal Telecom Leader
Resolving weekly RabbitMQ crashes, optimizing for a large connected-device fleet, and architecting horizontal scaling strategy.
RabbitMQKubernetesQuorum QueuesPrometheusGrafanaSupport options
AceMQ offers independent Zabbix support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and emergency response for servers your team runs, proactive reviews that find database, housekeeper and version problems first, managed Zabbix on your own infrastructure, and managed Zabbix on AceMQ infrastructure. Zabbix 6.0 LTS, 7.0 LTS and 7.4 are covered by AceMQ engineers working with partner Zabbix specialists. Fixes still come from Zabbix releases, and AceMQ has no access to Zabbix development.
You run it, we back you up
Best for: Teams that run Zabbix themselves and need a second pair of senior hands when the monitoring system misbehaves at 3am.
You run it, we watch it with you
Best for: Teams that want the oversized history table or the 6.0 server found in a review, not in an outage.
We run it in your cloud or data centre
Best for: Regulated estates that must keep monitoring data inside their own boundary and want someone else on the rota.
We host it and run it, as a service
Best for: Teams that want Zabbix without a Zabbix on-call rota.
| Who does what | Tier 1 24/7 support | Tier 2 Proactive monitoring | Tier 3 Managed, your infrastructure | Tier 4 Fully managed by AceMQ |
|---|---|---|---|---|
| Who runs Zabbix day to day? | Your team | Your team, with AceMQ reviews | AceMQ | AceMQ |
| Where does it run? | Your infrastructure | Your infrastructure | Your cloud account or data centre | AceMQ infrastructure |
| 24/7 incident response | Response targets from 15 minutes, by plan | Response targets from 15 minutes, by plan | Response targets from 15 minutes, by plan | Response targets from 15 minutes, by plan |
| Health checks and CVE alerts | On request | Scheduled | Included | Included |
| Patching and upgrades | Your team, AceMQ advises | Planned with AceMQ | Done by AceMQ | Done by AceMQ |
| Monitoring and on-call | Your team | Your team | AceMQ | AceMQ |
| Data, keys and accounts | Yours | Yours | Yours | Your data, hosted by AceMQ |
Every Tier can start as an ad hoc engagement or an annual partnership, and you can move up or down a Tier as your team changes.
One partner for Zabbix
Support is one part of what AceMQ does for Zabbix. The same engineers deliver consulting, health checks, migrations and end-of-life cover, and support the systems that usually run next to it.
AceMQ Zabbix support means 24/7 emergency response with response targets from 15 minutes, by plan, a written root-cause analysis after every P1, database, housekeeper, proxy and HA reviews, performance diagnosis and version planning, delivered by an AceMQ engineer with a partner Zabbix specialist. It does not include access to Zabbix development or patched builds, which AceMQ does not produce.
Zabbix sells five tiers, Silver to Global, from 8x5 to 24x7 coverage, and every subscription includes access to Zabbix experts. Choose Zabbix when you need the people who write the software. Choose AceMQ when you want an engineering team that learns your database, proxies and templates, 24/7 cover under one contract with your other platforms, or help alongside a Zabbix subscription you already hold. Both can run together.
Yes, with limits. Zabbix 6.0 LTS is in limited support until 28 February 2027, which Zabbix describes as critical fixes only. AceMQ keeps the server running, diagnoses incidents and plans the upgrade. It cannot supply fixes that Zabbix does not release for that version.
Support means your team still runs the server and has senior engineers to escalate to. Managed services means AceMQ also does the operational work on a schedule, on your infrastructure or ours, and holds the pager. Most teams start with support, add proactive reviews and move to managed later if they want to.
Yes. AceMQ works on Zabbix in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.
Every AceMQ proposal is tailored to your requirements: your Zabbix environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Zabbix is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.
Let's talk
Reactive cover, proactive reviews, or AceMQ running Zabbix for you on your infrastructure or ours. A senior engineer scopes it with you, and quote requests are answered within 1 hour.
Production incident right now?Email a Zabbix Architect
Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.
305-204-2607info@acemq.comPrefer to talk now? Call us directly or use the consultation tab to find a time that works.
