There is a wrong interpretation of the maxQueryMetrics with zabbix 5.0.4 and vcenter  7.0.1, 16850804

The new default value is 256 (as per [this vmware kb article]|Performance charts are empty and displays the error: Request processing is restricted by administrator (2107096) (vmware.com)].

Zabbix is querying the parameter but when it's not found misinterpreting that the value is still 64 and throwing an error in zabbix_server.log.

We have then set the value in the vcenter advanced configration explizit to 256 and the error is gone.

Before:

[<soapenv:Fault><faultcode>ServerFaultCode</faultcode><faultstring>'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted.</faultstring><detail><InvalidNameFault xmlns="urn:vim25" xsi:type="InvalidName"><name>config.vpxd.stats.maxQueryMetrics</name></InvalidNameFault></detail></soapenv:Fault>
1010350:20201130:101036.120 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
1010350:20201130:101036.120 maxQueryMetrics used default value 64
<QueryOptionsResponse xmlns="urn:vim25"><returnval>

After:

<key>config.vpxd.stats.maxQueryMetrics</key><value xsi:type="xsd:string">256</value></returnval></QueryOptionsResponse>
<QueryOptionsResponse xmlns="urn:vim25"><returnval><key>config.vpxd.stats.maxQueryMetrics</key><value xsi:type="xsd:string">256</value></returnval></QueryOptionsResponse>
<QueryOptionsResponse xmlns="urn:vim25"><returnval><key>config.vpxd.stats.maxQueryMetrics</key><value xsi:type="xsd:string">256</value></returnval></QueryOptionsResponse>
<QueryOptionsResponse xmlns="urn:vim25"><returnval><key>config.vpxd.stats.maxQueryMetrics</key><value xsi:type="xsd:string">256</value></returnval></QueryOptionsResponse>

 
Expected:

We would expect zabbix to verify which version of vcenter is queried due to different default settings from vmware.