Ad Widget

Collapse

Vmware monitoring Performance counter is not available

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • s.halin
    Junior Member
    • Jan 2018
    • 1

    #1

    Vmware monitoring Performance counter is not available

    Hello all,

    I have got trouble monitoring my vmware virtuals machines. The item about disk management are in "not supported" state because "Performance counter is not available"

    Here is the related key:
    vmware.vm.vfs.dev.write[{$URL},{HOST.HOST},scsi0:0,ops]

    Could anybody help me?

    Thanks in advance
  • troffasky
    Senior Member
    • Jul 2008
    • 567

    #2
    I have this also. Datastores are all discovered, read/write latency items are created and work, but datastore size and utilisation items all become Not Supported.
    VMware ESXi 6.5.0 build-8294253
    Zabbix 3.4
    This is just three ESXi servers monitored through one specific proxy. All others work fine. If I change one host to not use the proxy, it immediately starts working. Proxy has 4 collectors which according to 'top' spend most of their time idle, so I assume that means I have enough of them.
    Last edited by troffasky; 13-09-2018, 12:20.

    Comment

    • troffasky
      Senior Member
      • Jul 2008
      • 567

      #3
      This is logged:

      Code:
       15624:20180913:112035.588 cannot get refresh rate for Datastore "5af1d70c-ca86142b-8a9b-2c44fd88545c": A specified parameter was not correct: entity
       15624:20180913:112035.590 cannot get refresh rate for Datastore "5af44ce8-0b24cb44-b25b-2c44fd88545c": A specified parameter was not correct: entity
       15624:20180913:112035.591 cannot get refresh rate for Datastore "52fb067d-a6f16913-b0d6-2c44fd8854bc": A specified parameter was not correct: entity
       15624:20180913:112035.592 cannot get refresh rate for Datastore "5af1d624-b873010e-2a39-2c44fd88545c": A specified parameter was not correct: entity
       15624:20180913:112035.594 cannot get refresh rate for Datastore "5af1d672-27dbe732-5879-2c44fd88545c": A specified parameter was not correct: entity

      Comment

      • troffasky
        Senior Member
        • Jul 2008
        • 567

        #4
        OK, it's a bug, I will upgrade to 3.4.12.
        Last edited by troffasky; 13-09-2018, 12:34.

        Comment

        Working...