MVekslers, possible regression?

Hi,

The maxQueryMetrics is required to determine max number of DS prefcounters per request. But starting from vc6.0 this parameter is not configured out of the box. The VC uses default values (64 for vc60 and 256 for any new vc)

But vmware still keep ability to change this value via configuration of system.

At the result, we check the value of maxQueryMetrics and if we can't obtain the value, we write info to the log file as Debug entry (not an error or warning).

In short - this is normal behavior. (and hasn't changed for many years)

<edgar.akhmetshin>: "the value in our case for maxQueryMetrics is 256"

So was the value in our case.

thats why I was confused . The msg here implies that the number is invalid or that something else is wrong.

Hello Patrik,

Please confirm if value maxQueryMetrics is set manually or just a default value? Could you set it manually to the same level and test once again?

Regards,
Edgar

https://www.zabbix.com/documentation/6.4/en/manual/vm_monitoring#troubleshooting :

To support datastore capacity metrics, ensure that the value of the VMware vpxd.stats.maxQueryMetrics key is set to at least 64. For more information, see the VMware Knowledge Base article.

hi,

its defined in our system in the file web.xml and is 256

so if zabbix cannot detect this value how will it set the max number of DS prefcounters

edgar.akhmetshin  that url is not working there is a : at the end

Hi @patrik uytterhoeven,

Did you do it in both places as described in https://knowledge.broadcom.com/external/article?legacyId=2107096

?

no i am not able/allowed to change this parameter

thats why i was interested how zabbix would behave if it cannot detect this value

We set the default values