[ZBXNEXT-7717] VMware Guest uptime trigger should take power state into consideration. Created: 2022 May 14 Updated: 2024 Jul 18 Resolved: 2024 Jul 18 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Templates (T) |
| Affects Version/s: | 5.0.22 |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Jose A. Hernandez | Assignee: | Aleksandr Kotsegubov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
The VMware Guest VM trigger for restarts only takes uptime into account. If a VM is intentionally powered off, the uptime never goes above 0 so the trigger will create a false alarm that cannot be resolved. I assume this affects 6.x too. May I suggest the following? 1. Modify the existing VMware Guest has been restarted trigger to alert when both the uptime is less than 10 minutes AND the powerstate of the VM is PoweredOn 2. Setup a new Warning state trigger when a VM guest transitions from PoweredOn to PoweredOff state. 3. Setup a new Information state trigger when a VM guest transitions from PoweredOff to PoweredOn state.
|
| Comments |
| Comment by Aleksandr Kotsegubov [ 2024 Jun 06 ] |
|
1. The "VM has been restarted" trigger will be updated within the task
2. Separate triggers for turning on and off the VM will not be added. Currently, as part of task Thus:
|
| Comment by Aleksandr Kotsegubov [ 2024 Jul 18 ] |
|
The trigger will be updated within the task |