ZABBIX Forums - Zabbix Discussions and Feedback

How can fix template to get correct writeKB/S for each disks

bab — Sat, 13 Jun 2026 07:16:57 GMT

I am using follow template :

https://github.com/grundic/zabbix-di...erformance.xml

to find out amount write KB/S on disks but for example my virtual machine has 1 disk (sda) and it contains volume such as follow :

Code:

/dev/mapper/vg00-root   /                       xfs     defaults        0 0
/dev/mapper/vg00-backup /backup                 xfs     defaults        0 0
UUID=154dc742-6137-43bc-acae-d9e3e198b93c /boot                   xfs     defaults        0 0
UUID=2554-72EE          /boot/efi               vfat    defaults,uid=0,gid=0,umask=077,shortname=winnt 0 2
/dev/mapper/vg00-home   /home                   xfs     defaults        0 0
/dev/mapper/vg00-lateral /lateral                xfs     defaults        0 0
/dev/mapper/vg00-tmp    /tmp                    xfs     defaults,noexec,nodev,nosuid        0 0
/dev/mapper/vg00-usr    /usr                    xfs     defaults        0 0
/dev/mapper/vg00-var    /var                    xfs     defaults        0 0
/dev/mapper/vg00-swap   none                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults,noexec,nodev,nosuid        0 0
l

But after discovery on this host it find many items as writebyte/S ? Whta is the issue ? How can generate KB/S just for sda ?

File discovery not showing all filesystems on one Windows server

poldermonitor — Thu, 11 Jun 2026 10:49:35 GMT

Hello,

I actually already asked this on Reddit, but only just noticed there’s a dedicated Zabbix community here as well so reposting my question here.

I'm running into a strange issue with file discovery on one of my Windows servers and was hoping someone here might have seen this before.

The server has 43 disks, and all of them are detected correctly via disk discovery. However, with filesystem discovery (vfs.fs.discovery), only 11 filesystems are being discovered, while I expect around 46.
The odd part is that when I run the command locally on the server:

zabbix_agent2.exe -t vfs.fs.discovery

it correctly returns all filesystems.
Even more confusing: in Zabbix, I do see some of the expected entries, for example:

{"{#FSNAME}":"D:\\Clinical\\departmenta","{#FST YPE }":"NTFS","{#FSLABEL}":"[Clinical] - departmenta","{#FSDRIVETYPE}":"fixed"}

But very similar ones are missing, like this one:

{"{#FSNAME}":"D:\\Clinical\\departmentb","{#FST YPE }":"NTFS","{#FSLABEL}":"[Clinical] - departmentb","{#FSDRIVETYPE}":"fixed"}

(The names are slightly modified to avoid sharing company data.)

So it seems the agent can discover them, but for some reason Zabbix only processes or shows a subset.

Does anyone have an idea why one filesystem would be included while another nearly identical one is not? Could this be related to LLD filters, limits, or something else I'm overlooking?

Does anyone know how I can make sure all filesystems are discovered?

Best practice for monitoring the components of a Zabbix HA system

sleb — Thu, 11 Jun 2026 10:10:01 GMT

Hi all,

What is the best practice for monitoring the components of a Zabbix system composed of:
- 2 server nodes on high-availability (HA) configuration
- 2 proxy groups, each composed of 2 proxies.

I can't find any information on this topic.

I'm using version 7.4, and for now I'm using the following templates:
- “Zabbix proxy health by Zabbix agent” on the proxies,
- “Zabbix server health by Zabbix agent” for the server nodes.

Am I on the right way ?

Thanks a lot for your support
Séb

Zabbix 7.4.9 unable to get scheduled reports working.

rbpowell — Wed, 10 Jun 2026 18:54:41 GMT

I have an Ubuntu 24.04 running docker, my setup is a docker compose file with the following services PostgreSQL, Zabbix 7.4.9 Server, Nginx Web interface, Web Service, headless chrome, Agent 2, snmp Traps, Java Gateway, all running in same network subnet. I have added all of the variables for scheduled reporting. WebServiceURL, Allowed IP, Listening port, Frontend URL are all set, all testing shows everything working. When I run the test for the report I get this error:

2026/06/10 18:07:05.016034 received report request from 172.30.240.0:48568
2026/06/10 18:07:05.016498 making chrome headless request with parameters url: http://my.internal.com/zabbix.php?ac...shboardid=405& from=2026-06-09%2000%3A00%3A00&to=2026-06-10%2000%3A00%3A00, width: 1920, height: 1080 for report request from 172.30.240.0:48568
10 18:07:36.190650 Cannot fetch data.: dashboard failed to get ready, url: 'http://my.internal.com/zabbix.php?action=dashboard.print&dashboardid=405& from=2026-06-09%2000%3A00%3A00&to=2026-06-10%2000%3A00%3A00': Inspected target navigated or closed (-32000).

I can take the URL listed in the error and paste it into a browser and it opens the Dashboard in 2 secs. Guessing but the error sounds like something to do with chrome, but I have not been able to figure it out. Chrome is running and all tests shows it as working correctly and the configuration test all show good. I have even tried running chrome direct instead of a container on the server with the same error message.

Any help with this would be greatly appreciated.

Trigger on "average" but exclude spikes.

detniels — Wed, 10 Jun 2026 08:58:09 GMT

I am sampling some data every 10 seconds and wan't to trigger when all of the sampled values have been above 5 for a duration of 5 minutes.

Average doesn't help me, maybe because I am too dumb to use it.... But if all values returned during the 5 minutes are 1, except one value that is 100, the average trigger will fire, obviously.

What trigger function should I use?

(Zabbix 6.0.5)

Autoregistration with mTLS and proxies

olegus — Tue, 09 Jun 2026 17:57:40 GMT

Is it supported?
We decided to use mTLS on both legs (agent->proxy and proxy->server) and lose autoregistration feature. There is no mTLS option on Autoregistration setup page also. We are on 7.4.7.

Zabbix Agent 7.4 Installation on Solaris 11.4 version

B0329091 — Tue, 09 Jun 2026 10:04:19 GMT

i am trying to install zabbix agent on Solaris 11 but i didn't so pls give the complete guide for agent installation in solaris 11.4 server

VEEAM 13 - Template available

Hafamori — Tue, 09 Jun 2026 09:11:01 GMT

Has anyone been successful in monitoring VEEAM 13 B&R with zabbix? Supplied template is outdated.

Cannot connect to the database

Sandeep — Mon, 08 Jun 2026 12:51:36 GMT

Hi Everyone. I am new to Zabbix and trying to install zabbix 7.4 with mysql 8 on single node.
Installation went fine and all services came up without any issues and I am able to connect to the internet using localhost and creds through CLI.
But, coming to webserver, it throws error saying cannot connect to the database. Can someone please help me to fix the issue

Overriding Legend Strings in Graph widgets to make them shorter?

timg11 — Sat, 06 Jun 2026 16:39:05 GMT

I'm using Zabbix 7.0.22 to graph SNMP data from a Cisco SG200 26 port switch.

I'm only interested in the data throughput for some of the ports, so I used the graph widget, I added a data set for each port I want to have on the graph.

The host is Cisco SG-200-26. I use wildcard strings like Interface gi1(* Bits* in Item Patterns to match both sent and received bit/sec for a specific port.

The problem is the legend displays long strings like "Cisco-SG200-26: Interface gi5(Server Room E Shelf Switch): Bits received"
They take too much room, displaying the redundant part and truncating the relevant parts.
I'd like to override the legends and have a custom name like "gi5(Server Room E Shelf Switch): received"

I wasted several hours with AI trying numerous approaches, none of which worked.
Is there a human around here who knows how to do this?

Zabbix agent / agent2 on CentOS 9.7 - server cannot connect.

Motok — Thu, 04 Jun 2026 12:42:44 GMT

Hey there,
I have a working Zabbix server 7.0 LTS with some hosts, Windows and Linux, everything is going fine.
Today, I have just installed a new virtual machine with Linux CentOS 9.7 with Zabbix agent / agent2 (tried both) but i cannot connect from server.
They are both on same VLAN, server IP is 192.168.100.42 and client IP is 192.168.100.25.

When i m trying to netcat from server into client on port 10050 :

Code:

nc -zv 192.168.100.25 10050
myhost.domain.local [192.168.100.25] 10050 (zabbix-agent) : No route to host

But it s working when i m trying others ports, like 80 and 443 :

Code:

nc -zv 192.168.100.25 80
myhost.domain.local [192.168.100.25] 80 (http) open

I did checked the open ports on the client :

Code:

tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      2555/docker-proxy  
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      2533/docker-proxy  
tcp        0      0 0.0.0.0:10050           0.0.0.0:*               LISTEN      967/zabbix_agentd  
tcp        0      0 0.0.0.0:8022            0.0.0.0:*               LISTEN      952/sshd: /usr/sbin
tcp        0      0 0.0.0.0:62354           0.0.0.0:*               LISTEN      948/glpi-agent: wai
tcp6       0      0 :::443                  :::*                    LISTEN      2561/docker-proxy  
tcp6       0      0 :::80                   :::*                    LISTEN      2542/docker-proxy  
tcp6       0      0 :::10050                :::*                    LISTEN      967/zabbix_agentd  
tcp6       0      0 :::8022                 :::*                    LISTEN      952/sshd: /usr/sbin

I did tried to remove SELinux :

Code:

sestatus
SELinux status:                 disabled
getenforce
Disabled

I disabled the firewall iptables too :

Code:

iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination]

I m still stucked any ideas ?

Many thanks

Email notifications not working after sendgrid apikey rotation

beingomkardalvi — Thu, 04 Jun 2026 09:27:44 GMT

We have Zabbix deployed in a Docker container and recently updated the SendGrid password. Since then, Zabbix email notifications have stopped working, even after updating the new password in the media type configuration. I tested email sending manually from inside the container, and emails are being received successfully. However, when testing through the Zabbix media type, it fails with the following error: "Timeout was reached: Connection timed out after 40002 milliseconds."
Any idea how can I resolve it.?

Using below command I am able to receive email when I am trying inside container.

curl -X POST "https://api.sendgrid.com/v3/mail/send" -H "Authorization: Bearer abc" -H "Content-Type: application/json" -d '{"personalizations":[{"to":[{"email":"abc@xyz.com"}],"subject":"Test Email from Zabbix"}],"from":{"email":"xyz@abc.com"},"content":[{"type":"text/plain","value":"Test message from Zabbix server"}]}'

Ack message: add clickable link

muelli — Thu, 04 Jun 2026 09:23:08 GMT

Hi,

I am using an custom alert script that sends trigger messages to an external ticket system that opens tickets for zabbix alerts.
Upon opening, it returns an URL to the opened ticket, which is then added as an acknowledge message to the alert. However.... I would like for the link to be clickable, at the moment it is pure text.
Using HTML does not work, since it is not interpreted.
Any ideas on how to make the link clickable?

Thanks!

Problem Widget - BGP Peer Not Established - ASN #

jimmy.mccubbins — Wed, 03 Jun 2026 15:31:36 GMT

We have a template to look for when we lose BGP connection to devices and its working. We want to take it a step further though and only see specific ASN's instead of all of them.
In the Problems Page of the BGP Template we can hover over the "question mark" and it will show the ASN. When I build the Problem Widget, it does not show the ASN number. How do I get the Problem Widget to display the ASN number of the connection not established.

Zabbix proxy how to disable collect data about VMs in vmware collector

sergzh1703 — Wed, 03 Jun 2026 13:15:21 GMT

Zabbix version 7.0.26.
Is it possible to disable virtual machine data collection in the "VMware Collector"? I have LLD disabled for VMs in the templates, but in the proxy log, I see that the collector continues to collect data from vCentra for VMs.

625506:20260603:135723.312 In vmware_service_get_vm_folder() folder id:'group-v383782'
625506:20260603:135723.313 End of vmware_service_get_vm_folder(): vm folder:vcd
625506:20260603:135723.313 In vmware_vm_get_nic_devices()
625506:20260603:135723.313 vmware_vm_get_nic_device_ips() empty list of guest ips for mac:00:50:56:01:1f:98
625506:20260603:135723.313 End of vmware_vm_get_nic_devices() found:1
625506:20260603:135723.313 In vmware_vm_get_disk_devices()
625506:20260603:135723.313 End of vmware_vm_get_disk_devices() found:1
625506:20260603:135723.313 In vmware_vm_get_file_systems()
625506:20260603:135723.314 End of vmware_vm_get_file_systems() found:2
625506:20260603:135723.314 In vmware_vm_get_custom_attrs()
625506:20260603:135723.314 End of vmware_vm_get_custom_attrs() attributes:0
625506:20260603:135723.314 In vmware_service_get_alarms_data(), func_parent:'vmware_service_create_vm'
625506:20260603:135723.314 End of vmware_service_get_alarms_data() func_parent:'vmware_service_create_vm' found:0 total:110
625506:20260603:135723.314 End of vmware_service_create_vm():SUCCEED
625506:20260603:135723.314 In vmware_service_create_vm() vmid:'vm-1500176'
625506:20260603:135723.314 In vmware_service_get_vm_data() vmid:'vm-1500176'
625506:20260603:135723.355 End of vmware_service_get_vm_data():SUCCEED
625503:20260603:135723.356 End of vmware_tags_linked_id() ids:0
625503:20260603:135723.356 End of vmware_tags_get() found tags:0
625503:20260603:135723.357 In vmware_tags_get() obj_id:vm-1891439
625503:20260603:135723.357 In vmware_tags_linked_id() obj_id:vm-1891439
625506:20260603:135723.358 In vmware_service_get_vm_snapshot()
625506:20260603:135723.358 In vmware_vm_snapshot_collect() count:0
625506:20260603:135723.358 vmware_vm_snapshot_collect() empty list of fileKey
625506:20260603:135723.358 End of vmware_vm_snapshot_collect():FAIL
625506:20260603:135723.358 End of vmware_service_get_vm_snapshot():FAIL