Ad Widget

**Heilig** · 26-08-2013, 10:52

Servers monitored through zabbix proxy or directly?

You need to understand how and check what compares zabbix. For the first, you can use the documentation and https://support.zabbix.com/browse/ZBX-4500. For a second, you can use macros {ITEM.VALUE<1-9>} and {TIME} (https://www.zabbix.com/documentation...ed_by_location), and then compare the values to find out, there really is a difference or not.

**mushero** · 26-08-2013, 17:57

Originally posted by Heilig

Servers monitored through zabbix proxy or directly?

No proxy.

You need to understand how and check what compares zabbix. For the first, you can use the documentation and https://support.zabbix.com/browse/ZBX-4500. For a second, you can use macros {ITEM.VALUE<1-9>} and {TIME} (https://www.zabbix.com/documentation...ed_by_location), and then compare the values to find out, there really is a difference or not.

Yes, familiar with that feature, which is why I show the lists that includes the times Zabbix received the data in Latest Data - correct me if I'm wrong, but the timestamp is when Zabbix receives it and the trigger checks the value - you can see they never differ by more than a couple seconds, yet we have 120 second trigger alerting.

And only on one set of customers/servers, not any others, which is odd. We've seen a few issues on fuzzytime but I think related to proxies or other issues, but is consistently every day or two on these servers, so very odd.

**Heilig** · 28-08-2013, 13:59

Interesting. )
The problem happens on the same servers in the same time?
Note the phrase of ZBX-450:
"... AT THE TIME TRIGGERS ARE PROCESSED".
Check the graphics from "Template App Zabbix Server", perhaps they have bursts at the same time.

**mushero** · 28-08-2013, 17:40

But isn't the time processed when it's received, or very close to it ? I can't imagine the server is more than 120 seconds late processing this data when the received time in the DB is exact.

And if it was very busy or far off, we'd see this on all servers, not this customer.

**Heilig** · 29-08-2013, 18:48

Yes you are right. Do you use notification? Can you spend a little time for testing? Include two macro {ITEM.VALUE} and {TIME} in the email message which generates by this trigger.

**mushero** · 29-08-2013, 19:07

Originally posted by Heilig

Yes you are right. Do you use notification? Can you spend a little time for testing? Include two macro {ITEM.VALUE} and {TIME} in the email message which generates by this trigger.

We don't, but we can try this - this problem has happened less lately and may be due to server very busy, but this is a good idea to notify on it to see the real issue (though I'd think we could see in the event). Thanks.

**mushero** · 17-06-2014, 10:19

Seems I may understand why.

Can someone tell me WHEN triggers are evaluated ? We always think it's when values change, but where does it happen ? You'd think it's when new values arrive at the Zabbix server but I'm now thinking this is not true.

Looking at the code, it seems the poller process just store the item data in the cache and the cache sync/flush process actually evaluates the functions and sets trigger values.

In our case and nearly 100,000 triggers and 600 NVPS I think this process is getting behind, especially during housekeeping, and thus my fuzzytimes are getting delayed and thus the trigger fires.

Am I wrong ? Can someone tell me how it works for real, i.e. the path from receiving agent data and evaluating a trigger with fuzzytime?

Ad Widget

Fuzzytime() false alerts

Fuzzytime() false alerts

Comment

Comment

Comment

Comment

Comment

Comment

Comment