[ZBX-19603] False alert : VM host has just been restarted - for a host has newer been or has been off for a long time. Created: 2021 Jun 24 Updated: 2023 Dec 22 Resolved: 2023 Dec 22 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | None |
| Affects Version/s: | 5.2.7rc1 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Michał Panasiewicz | Assignee: | Oleksii Zagorskyi |
| Resolution: | Commercial support required | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Template: "VMware Guest" Resolution
{VMware Guest:vmware.vm.uptime[{$VMWARE.URL},{$VMWARE.VM.UUID}].last()}>0s and
{VMware Guest:vmware.vm.uptime[{$VMWARE.URL},{$VMWARE.VM.UUID}].last()}<=10m
|
| Comments |
| Comment by Oleksii Zagorskyi [ 2021 Jun 28 ] |
|
Original template trigger is:
{VMware Guest:vmware.vm.uptime[{$VMWARE.URL},{HOST.HOST}].last()}<10m
Show graph and values list collected by the item at the time then the trigger generated problem event. |
| Comment by Michał Panasiewicz [ 2021 Jun 30 ] |
|
Original trigger catch all power off machine all the time. |
| Comment by Oleksii Zagorskyi [ 2023 Dec 22 ] |
|
Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support (https://zabbix.com/support) or consultancy services. Alternatively, you can also use our community channels (https://www.zabbix.com/community) for assistance. With that said, we are closing this ticket. Thank you for understanding. |