Zabbix Server Version: 7.0.17
As the title suggests, I am trying to create an item that determines the free space of the mounted file systems on some Ubuntu servers, each with a couple of mounted file systems.
As it stands currently, the hosts (my ubuntu servers) are inheriting...
5 results in 0.0026 seconds.
-
zabbix_mouse_123 started a topic Item that returns the remaining mounted space without concern for reserved space.in Zabbix HelpItem that returns the remaining mounted space without concern for reserved space.
-
nilsjman started a topic Setting (manual) thresholds for overall disk space, RAM, CPUin Zabbix HelpSetting (manual) thresholds for overall disk space, RAM, CPU
First post!
Zabbix Server 5.0.2
We're monitoring several (~90) Windows HyperV VMs with mainly Windows Server 2016/2019. With filesystem discovery (vfs.fs.discovery) everything works fine.
The sizes of the VMs (disk space, RAM, CPU) are defined in a contract.... -
vfs.fs.discovery data not shown in Zabbix Server
Hi,
I'm rather new to Zabbix and I'm running into this issue.
Server is 2.2.6-1 running on RHEL6.5.
The agent I'm running into this issue is version 2.0.12 on Ubuntu 10.04 LTS. The filesystem discovery isn't working on this agent. When debug logging is enableb I can... -
vfs.fs.size works directly on agent but ZBX_NOTSUPPORTED when requested from server
I'm trying to learn more about low-level discovery, and luckily I have a problem to tackle
This is a simple test configuration that I run on a single computer utilizing virtualbox VM instance where I run server, and agent is running directly on my personal laptop.
Server... -
vfs.fs.discovery on Windows, additional macro
I would like to see an additional macro added to the vfs.fs.discovery key on Windows. Currently vfs.fs.discovery returns 2 macros, #FSNAME and #FSTYPE.
However currently #FSNAME returns the C drive as C:\. Hence the #FSNAME macro works great for the other vfs.* keys. But most Windows...
