-
Problem report
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
Support backlog
There are many items in VMware template that perform discard only after the preprocessing, while it could be acceptable if subset of large data is retrieved it is not the case and just done in general. This leads to unnecessary heavy javascript and JSONPath being performed, thus utilizing CPU and memory for no reason.
Expected:
If data is going to be discarded for sure there is no need to transform it using javascript. If need subset then retrieve it with JSONPath if possible, check for discard and then perform heavy javascript.
For example:
See top.total_ms
Top.total_ms: itemid:50635 total_ms:370 itemid:50628 total_ms:370 itemid:50530 total_ms:370 itemid:50488 total_ms:360 itemid:50586 total_ms:340 itemid:50537 total_ms:330 itemid:50579 total_ms:310 itemid:50481 total_ms:240 itemid:50484 total_ms:100 itemid:50786 total_ms:90 itemid:50678 total_ms:80 itemid:50670 total_ms:80 itemid:50590 total_ms:80 itemid:50582 total_ms:80 itemid:50638 total_ms:80 itemid:44058 total_ms:70 itemid:50746 total_ms:70 itemid:50443 total_ms:70 itemid:50732 total_ms:70 itemid:50631 total_ms:60 itemid:39807 total_ms:60 itemid:50724 total_ms:50 itemid:50778 total_ms:50 itemid:50692 total_ms:40 itemid:50541 total_ms:40
select items.itemid,items.key_,hosts.name from items join hosts on hosts.hostid=items.hostid where itemid in (50530,50579,50
628,50635,50586,50537,50488,50678,50746,50481,50786,50631,50724,44058,50484,50541,50590,50582,50492,50732,50670,39807,47554,50778,5
0443
+--------+----------------------------------------------------------------+---------------------------+
| itemid | key_ | name |
+--------+----------------------------------------------------------------+---------------------------+
| 39807 | zabbix.nodes.discovery | Zabbix server |
| 44058 | zabbix.proxy.discovery | Zabbix server |
| 47554 | zabbix.proxy.groups.discovery | Zabbix server |
| 50443 | vmware.hv.connectionstate[{$VMWARE.URL},{$VMWARE.HV.UUID}] | vm-esx-02.zabbix.sandbox |
| 50481 | vmware.hv.sensors.discovery | vm-esx-02.zabbix.sandbox |
| 50484 | vmware.hv.healthcheck.discovery | vm-esx-02.zabbix.sandbox |
| 50488 | vmware.hv.serial.number.discovery | vm-esx-02.zabbix.sandbox |
| 50492 | vmware.hv.connectionstate[{$VMWARE.URL},{$VMWARE.HV.UUID}] | vm-esx-01.zabbix.sandbox |
| 50530 | vmware.hv.sensors.discovery | vm-esx-01.zabbix.sandbox |
| 50537 | vmware.hv.serial.number.discovery | vm-esx-01.zabbix.sandbox |
| 50541 | vmware.hv.connectionstate[{$VMWARE.URL},{$VMWARE.HV.UUID}] | vm-esx-03.zabbix.sandbox |
| 50579 | vmware.hv.sensors.discovery | vm-esx-03.zabbix.sandbox |
| 50582 | vmware.hv.healthcheck.discovery | vm-esx-03.zabbix.sandbox |
| 50586 | vmware.hv.serial.number.discovery | vm-esx-03.zabbix.sandbox |
| 50590 | vmware.hv.connectionstate[{$VMWARE.URL},{$VMWARE.HV.UUID}] | vm-witness.zabbix.sandbox |
| 50628 | vmware.hv.sensors.discovery | vm-witness.zabbix.sandbox |
| 50631 | vmware.hv.healthcheck.discovery | vm-witness.zabbix.sandbox |
| 50635 | vmware.hv.serial.number.discovery | vm-witness.zabbix.sandbox |
| 50670 | vmware.vm.state[{$VMWARE.URL},{$VMWARE.VM.UUID}] | xp64-sp2 |
| 50678 | vmware.vm.tools[{$VMWARE.URL},{$VMWARE.VM.UUID},status] | xp64-sp2 |
| 50724 | vmware.vm.state[{$VMWARE.URL},{$VMWARE.VM.UUID}] | debian-1 |
| 50732 | vmware.vm.tools[{$VMWARE.URL},{$VMWARE.VM.UUID},status] | debian-1 |
| 50746 | vmware.vm.consolidationneeded[{$VMWARE.URL},{$VMWARE.VM.UUID}] | migration_test |
| 50778 | vmware.vm.state[{$VMWARE.URL},{$VMWARE.VM.UUID}] | migration_test |
| 50786 | vmware.vm.tools[{$VMWARE.URL},{$VMWARE.VM.UUID},status] | migration_test |
+--------+----------------------------------------------------------------+---------------------------+
For example:
Value is:
7.0.3
It does not need preprocessing if unchanged
- related to
-
ZBX-26301 After upgrade to zabbix server 7.0.10 Still keep consumed memory.
-
- Closed
-