False alert : VM host has just been restarted

[Markku]

Ok some education is apparently needed.

First, you need to concentrate on one item at the time. That's normal troubleshooting methodology. Don't get confused by 460 or whatever hosts at the same time.

The trigger functions are evaluated against the data values for the items whenever the item receives a data value. Thus, when troubleshooting a specific trigger for a specific item, we need to check what data values have been present. The Graph link at the end of the line will open the graph of the data values, and then on top right there is a menu where you select Values.

Then copy like the 10 last timestamps and data values (as text, please don't paste so many huge pictures, it's difficult to read the post) here and check what you can see from them.

Markku

[_sSiDs_]

i have uploaded fresh template VM from version 5.4
and see 1 trigger is different
last(/VMware Guest/vmware.vm.guest.osuptime[{$VMWARE.URL},{$VMWARE.VM.UUID}])<10m there OS before uptime. foes it make any sense?
with that trigger enables i didnot see any problems.
but when i enabling second trigger

 VMware: {HOST.HOST} has been restarted (uptime > 0)                 last/VMware Guest/vmware.vm.uptime[{$VMWARE.URL},{HOST.HOST}])<0

there became massacre in PROBLEMS

[_sSiDs_]

Cannot evaluate function last(/52384e85-17dd-ba01-4629-78693d9ba181/vmware.vm.guest.osuptime[{$VMWARE.URL},{$VMWARE.VM.UUID}]): item is not supported.

[_sSiDs_]

looking trough all forum....this issue are migrating since version 2.3 it is really odd, that this could be simply fixed.
i wee keep my nervous system in idle....and just disable all this shit.

[_sSiDs_]

i think i fix it. need to wait and watch.

[_sSiDs_]

so,PROBLEM comes, then get RESOLVED...then since several minutes again PROBLEM and again RESOLVED.

[_sSiDs_]

i see that there 4 of triggers called "uptime". Actually I am new to those deep and high-skilled configurations, sorry)
I will be appreciate if anybody to point me where to source the problem.

[_sSiDs_]

and one more and i think important....in Lastest data---- no infp about UPTIME
dont know why there no data....
there no agents on guest VMs
just created host CLUSTER vCenter and zabbix pulled all hosts and VMs

[Markku]

i see that there 4 of triggers called "uptime". Actually I am new to those deep and high-skilled configurations, sorry)
I will be appreciate if anybody to point me where to source the problem.

No, in that picture there are only two triggers (as shown in the Triggers column).

You need to know that items are not triggers. Item is the thing that has some value, and trigger is the expression that gets evaluated every time there is a new value for the item that is referenced in the trigger expression.

Markku

[Markku]

so,PROBLEM comes, then get RESOLVED...then since several minutes again PROBLEM and again RESOLVED.

What is the item that has the trigger?

What were the values for the item around the time of triggered problem?

What is the actual trigger expression in that case?

Markku

[Akraz]

I am having this same issue.

Whenever a network device reaches 1 year, 18 weeks, 6 days, 2 hours, 30 minutes, i get an alert from zabbix that the uptime has been restarted.

This uptime must translate to an epoch value that zabbix cannot reach and resets the timer.