ZABBIX Forums - Zabbix Suggestions and Feedback

Zweep: A self-hosted Android alerting solution for Zabbix

Nicodroid — Wed, 07 Oct 2026 14:24:20 GMT

Hi everyone,

while looking through the community for existing solutions to manage Zabbix alerts from mobile devices, I found several interesting options, but none that fully matched what I was looking for.

So, over the past few weeks, I started working on Zweep, an open-source, self-hosted alerting system for Zabbix, with an Android app for receiving alerts, viewing active problems, and acknowledging them directly from the phone.

The idea came from a practical need: being able to receive Zabbix alerts without relying on third-party cloud services, using a channel dedicated exclusively to Zabbix rather than mixing these notifications with those from other services.

The basic flow is:

Zabbix Action → Zweep media type → Zweep server → Android app

The main goals are:

keeping alert delivery completely self-hosted;
avoiding Firebase/FCM and other third-party notification services;
not storing Zabbix credentials on mobile devices;
allowing operators to view and acknowledge problems directly from the app (which can also be useful for quickly stopping an escalation);
leaving recipients, retries, timing, and escalation logic to Zabbix Actions.

I’m aware that Zabbix has announced an official mobile app. Zweep is not intended to replace it or compete with its broader features. The goal is rather different: to provide a completely self-hosted alert-delivery system that can continue working even without Internet access (as long as the Zweep server and the devices can reach each other over the internal network). The app also makes it possible to quickly keep track of notifications and the problems that generated them, without having to open the full Zabbix dashboard every time.

For transparency, my professional background is mainly in systems administration, networking, and Zabbix rather than software development. Zweep started from a real operational need, and I developed it iteratively with significant help from AI-based coding tools.I’ve reviewed and tested the project’s behaviour and added automated tests, security checks, dependency scanning, and an SBOM. I’m sharing the project because I think there may be similar use cases where it could be useful.

If anyone would like to try it in a lab environment, I’d be very interested to hear what works, what doesn’t, and what you think could be improved.

The project is available on GitHub:

https://github.com/N1k0droid/zweep

Thanks for taking a look!

"Proxmox VE by HTTP" duplicates alarm on storages.

Pigi_102 — Wed, 07 Oct 2026 06:57:32 GMT

Hello all,
I have a three nodes cluster where, among most other external storages, I have a local zfs storage on every node.
One of three nodes have this local storage almost full while others have it fine ( but I think this also happens on external storages).
So, to better explain, this is the situation:

Code:

=== Storage of: pve1 ===
LocalZfs: Total=67GB, Used=61GB, Free=7GB (Active: 1)

=== Storage of: pve2 ===
LocalZfs: Total=67GB, Used=3GB, Free=65GB (Active: 1)

=== Storage of: pve3 ===
LocalZfs: Total=67GB, Used=3GB, Free=64GB (Active: 1)

This should lead to an error on only pve1 but instead:

Is this something that could be corrected In someway ?
Who should I ask, eventually ?

Thanks in advance

Pierluigi

Allow setting mysql connection Options

cbergmann — Tue, 06 Oct 2026 14:26:47 GMT

Hi,

we are using the PAM module for authentication against our MariaDB cluster.
We also want to monitor that authentication with Zabbix.

Unfortunately this seems to be impossible.
At first we got the error "this authentication plugin is not supported". This is because by default the PAM module for mariadb uses the dialog authentication plugin which is not supported by go-sql-driver. After adding "pam_use_cleartext_plugin" to the mariadb config it now uses the "mysql_clear_password" authentication plugin. Unfortunately enabling this requires setting "allowCleartextPasswords=1" in the DSN. But I found not way of passing this DSN parameter through the zabbix agent.

If there is a way I could not find it would be highly appreciated.

kind regards
Clemens

Unsupported DB! timescaledb version 23002 is newer than 22999

splarv — Tue, 06 Oct 2026 12:09:56 GMT

Hi all.
We use Debian 13.7 and PostgreSQL from the Debian PGDG repository. There are TimescaleDB in the PGDG repository with versions: 2.30.0+dfsg-1.pgdg13+1, 2.30.1+dfsg-1.pgdg13+1, 2.30.2+dfsg-1.pgdg13+1. There is not 2.29 version. Zabbix used from the zabbix repository:
http://repo.zabbix.com/zabbix/7.4/stable/debian

The problem is:

983233:20261006:150005.457 using configuration file: /etc/zabbix/zabbix_server.conf
983233:20261006:150005.472 Unsupported DB! timescaledb version 23002 is newer than 22999
983233:20261006:150005.472 TimescaleDB version is too new. Recommended version is up to TimescaleDB Community Edition 2.29.
983233:20261006:150005.474 Zabbix Server stopped. Zabbix 7.4.15 (revision bd350f540cd).

Why do you artificially restrict to 2.29? 2.30 is the minor version upgrade so it is will work with 2.30 too. May be you want to guarantee zabbix working, but you measures guarantee only that zabbix will not working. Now I have to drop database and recreate without TimescaleDB, this is not good.

Proxmox VE by HTTP (8.0.0rc1): hardcoded 10m/10s on per-disk "Get info" causes issues

broth-itk — Thu, 01 Oct 2026 22:31:26 GMT

Dear Zabbix team,

in the "Proxmox VE by HTTP" template (8.0.0rc1), the item prototype Node [{#NODE.NAME}]: Disk [{#DISK.NAME}]: Get info has a hard-coded update interval of 10m and a timeout of 10s. The existing macro {$PVE.PARAMS.INTERVAL.DISK} (1h) is only used by the Disks discovery rule, not by this prototype.

Every disk gets its own item that requests the same URL, /nodes/{#NODE.NAME}/disks/list, and extracts its own entry by JSONPath. On a node with 58 disks, that is 58 identical requests every 10 minutes. On my node a single pvesh get /nodes//disks/list takes 14s (about 5.6s CPU), so every request runs into the 10s timeout, and the dependent items (Model, Serial, Type, Vendor) go unsupported. In addition, the constant stream of these requests keeps the node busy permanently. The discovery rule and SMART status also use the hard-coded timeout of 10s.

Suggestions:

A) Quick fix: change the hard-coded values to {$PVE.PARAMS.INTERVAL.DISK} (1h) and a timeout of 60s. Static data like model and serial does not need a 10m interval, and it matches the SMART interval.

B) Add macros for the interval and the timeout (e.g. {$PVE.TIMEOUT.DISK}), so they can be adjusted per host without cloning the template.

C) Cleaner: let the discovery rule (which already fetches /disks/list) or one master item per node fetch the list once, and make the per-disk items dependent items with JSONPath. That replaces N redundant requests with one and avoids the timeout problem entirely.

Happy to test any of these on my setup. Keen to hear your thoughts.

Best regards,
Bernhard

Monitoring same host from different locations

np_unmu — Wed, 30 Sep 2026 14:43:03 GMT

Hi Zabbix Community,

we are currently redesigning parts of our monitoring environment and I would like to hear how others handle the following situation and what is considered best practice in Zabbix.

We are running Zabbix 7.4 with a central Zabbix server and multiple active proxies, usually one proxy per customer/site.

Most customer hosts are assigned to their local Zabbix proxy because the proxy has access to the internal network.

However, for many hosts we also need checks from an external perspective, ideally directly from the central Zabbix server.

Two typical examples: Example 1 – Firewall

The firewall host is monitored by the customer's Zabbix proxy.

Internal checks:

SNMP
interfaces
CPU/memory
VPN status
other firewall-specific metrics

These checks should obviously be performed by the customer's proxy.

At the same time, we would like to monitor the public WAN IP from outside, for example:

ICMP availability
packet loss
response time

This check should be performed by the central Zabbix server, because we want to know whether the customer's Internet connection/public IP is reachable from outside.

If the firewall host is assigned to the customer's proxy, icmpping is also executed by that proxy, which does not give us the external perspective we need. Example 2 – Linux web server

A Linux VM is monitored internally using the Zabbix agent / active checks through the customer proxy.

For the same server/application we also want to monitor:

public HTTPS URL availability
HTTP response
SSL certificate
response time

These checks should be performed externally by the central Zabbix server.

Again, because the host is assigned to the customer proxy, HTTP/Web checks are normally executed by that proxy.

What we would ideally like

Conceptually, we would like something like this:
Host: CUSTOMER-WEB01
Monitored internally by: CUSTOMER-PROXY

Agent / SNMP / internal checks
-> CUSTOMER-PROXY

URL / SSL / public ICMP checks
-> ZABBIX-SERVER

In other words, selecting the execution location per item, item type, template or check rather than only per host.

As far as I understand, Zabbix currently assigns the monitoring responsibility at host level, so there is no native "execute this item on the server instead of the assigned proxy" option. Solutions we are currently considering

1. Separate logical hosts

For example:
CUSTOMER-FW01
monitored by CUSTOMER-PROXY
SNMP / internal monitoring

CUSTOMER-FW01-EXTERNAL
monitored by ZABBIX-SERVER
public ICMP monitoring

and:
CUSTOMER-WEB01
monitored by CUSTOMER-PROXY
OS / agent monitoring

CUSTOMER-WEB01-WEB
monitored by ZABBIX-SERVER
HTTPS / certificate / external availability

This seems to be the most native Zabbix solution, but it creates additional hosts representing the same physical system/service.

2. Central custom collector + trapper items

Another option would be to keep everything on the original host and run a central script/service on the Zabbix server.

The collector would perform the external checks and push the results back into trapper items on the original host.

This keeps all data/problems on one host, but obviously requires custom logic outside the normal Zabbix item execution model. Existing feature requests

I also found several existing feature requests that seem to describe almost exactly this use case:

ZBXNEXT-5772 – Allow set "Monitored by proxy" per Item
ZBXNEXT-4531 – Proxy: ability to configure items to be monitored out of proxy (directly by Zabbix Server)
ZBXNEXT-8201 – Checkbox to poll item from the server instead of the proxy
ZBXNEXT-2282 – Monitoring Host Items by different proxies

As far as I can see, these requests are still unresolved.

Questions

How do you handle this in larger Zabbix environments?

Is using separate logical hosts for the different monitoring perspectives still the recommended/best-practice approach?

For example:
FW01
FW01-External

WEB01
WEB01-External

Or is there a newer/native way in Zabbix 7.4 to execute selected checks on the Zabbix server while the host itself is monitored by a proxy?

Is there any way to select a Zabbix proxy/server per item, template, Web Scenario or similar?

For people using separate hosts: how do you organize them so that problems, dashboards, tags and services still clearly show that both hosts belong to the same physical device or service?

And finally, with Zabbix 8.0 LTS approaching:

Are there any plans in Zabbix 8.0, or in a later release, to support selecting the monitoring location (Zabbix server / proxy / proxy group) on item level rather than only on host level?

If not, are the feature requests mentioned above still considered the intended direction for solving this limitation, or is there another architectural approach planned for Zabbix 8?

I found some older discussions where using two host configurations (internal/external) was suggested, but I would be interested to know whether this is still how people solve this today, especially in larger environments with many customer proxies.

Thanks!

Feature request: undo feature for template deletion

mikeely — Tue, 22 Sep 2026 00:11:19 GMT

Sure, for the default templates a user can simply redownload it, but if a user deletes a custom template then restoring it is a grab-bag of maybe pulling from binlogs, etc. Fraught, generally.

Proposal: Create a temporary "trash" type storage for deleted templates, allowing users to restore any templates deleted within a fixed period - perhaps 30 days since the templates themselves aren't very big.

Zabbix server preset graph lack of logic

Marcin_k — Sun, 20 Sep 2026 08:15:01 GMT

Zabbix Server 7.4: the preset graph for the zabbix-server host doesn't make any sense. Why is the grey area marked as total?

how to alert notification configure in zabbix

Networkmonitor — Tue, 15 Sep 2026 07:16:14 GMT

alert notification configure in zabbix ?

Dell Server IDrac Custom Template Required for all Dell servers

prabhudas — Tue, 15 Sep 2026 07:08:08 GMT

Hi Team Please suggest good template for Dell Server IDrac Custom data required??