[ZBX-22295] In the vmware.vm.discovery key, the {#VM.POWERSTATE} macro is not returning. Created: 2023 Feb 02 Updated: 2024 Apr 10 Resolved: 2023 Feb 28 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S), Templates (T) |
Affects Version/s: | 6.0.13, 6.2.7, 6.4.0beta6 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Major |
Reporter: | Rafael Magalhães | Assignee: | Michael Veksler |
Resolution: | Won't fix | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
VMWare 7.0.3 |
Attachments: |
![]() ![]() ![]() |
Team: |
Description |
I'm trying to create a filter in the virtual machines discovery rule so that it ignores turned-off VMs, but I verified through the Zabbix Proxy log capture that the discovery is not returning the macro {#VM.POWERSTATE}. |
Comments |
Comment by Edgar Akhmetshin [ 2023 Feb 03 ] |
Hello Rafael, Provide to the issue:
Regards, |
Comment by Rafael Magalhães [ 2023 Feb 03 ] |
Hi Edgar,
[ { " ":"501d969f-4342-4b0c-5f35-910212b6c1bb", ":"501d221b-d20b-297c-de84-e39eace17e22",
|
Comment by Michael Veksler [ 2023 Feb 06 ] |
Hello Rafael, The macros VM.POWERSTATE was introduced in Be so kind to provide the json for v6.2 and newer. Regards, Michael |
Comment by Michael Veksler [ 2023 Feb 28 ] |
Closing this for now, if you have any more questions, feel free to reopen this ticket! |