Ad Widget

Collapse

Problem with triggers prototypes

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dmn653
    Junior Member
    • Jan 2025
    • 2

    #1

    Problem with triggers prototypes

    Hello everyone,
    Have a new installation of Zabbix 7.0 on MariaDB 11. I have configured VMware template to autodiscovery my ESXi environment, seems like all works fine except one thing.
    In template VM Guest triggers prototypes for low disk space and critical disk space are work only on *unix systems. For all discovered Windows machines triggers from prototypes doesn't created. All data related to FS discovery from item prototypes are available in monitoring for each host in % and bytes.
    Tried to clone template and recreate items discovery and triggers prototypes, but with same result. What I'm doing wrong? How to start Zabbix create triggers from prototypes for VM with Windows Servers guest OS?
    Have an Windows Server 2019/2022 and FS ntfs/ReFS.
  • ismail.atmaca
    Junior Member
    • Jan 2025
    • 2

    #2
    We have a similar problem, does anyone have any ideas? At what stage could there be a deficiency? While Linux VMs create disk space triggers and reports, Windows VMs do not create disk space triggers.
    Click image for larger version

Name:	sc1.png
Views:	129
Size:	44.0 KB
ID:	497183


    Comment

    • ismail.atmaca
      Junior Member
      • Jan 2025
      • 2

      #3
      I think the solution link is.

      Same error with 7.0.5.
      I found if I wrapped {FSNAME} in single quotes first, '{FSNAME}' then wrapped back in double quotes "'{#FSNAME}'" it worked as intended and I have my guest volumes reporting.

      Code:max(/VMware Guest/vmware.vm.vfs.fs.size[{$VMWARE.URL},{$VMWARE.VM.UUID},{#FSNAME},pfree],5m)<{$VMWARE.VM.FS.PFREE.MIN.CRIT:"'{#FSNAME}'"} and {$VMWARE.VM.FS.TRIGGER.USED:"'{#FSNAME}'"}=1


      Comment

      • dmn653
        Junior Member
        • Jan 2025
        • 2

        #4
        Thx a lot. It works.

        Comment

        Working...