(In theory an isolated server should not be able to send notifications. Otherwise, you will only be notified on the first change.Īlso see official documentation for a complete list of available trigger functions. Zabbix Server connectivity issues Template App Zabbix Server Zabbix Server is network isolated Template App Zabbix Proxy No connection from proxy Make proxy trigger dependent on this trigger in order to avoid misleading notifications. In that case, if an item goes from 0 to 150 to 300, you will be notified on both changes. I am following this documentation to check the functions available. I need to compare between my item's value and check if it is 2 minutes earlier than the current timestamp. I don't think there is an actual function for the current time of the zabbix server, but you can retrieve it from an agent using the system.localtime key. You probably also want the trigger to generate multiple successive PROBLEM events by selecting the checkbox on the right of "Multiple PROBLEM events generation". fuzzytime() you mentioned is suposed to be between the timestamp of the item and the zabbix's time. If you're looking for a difference between each check, looking it storing values as a delta, rather than the retrieved value.
The possibility to monitor time deviation using the standard active-mode agent is another very important reason.If you only wish to see whether the last value differs from the previous value, you should use the diff() function, like so: It would be useful to allow specifying the range further - whether it's on both sides of now (), or whether only > or < of now () counts. I understand that it could cause to some problems (for example, false positives if some values have been buffered and delayed by active-mode agents and intermediate proxies), but these problems much more predictable and understandable than the current behaviour. Description The fuzzytime () trigger function allows to check for item value in/out of a specific time range, compared to the time on the Zabbix server. In result, we could use this metric by active-mode agents, too. I believe that the behaviour of this trigger function should be modified according to documentation. Key moment: "differs from the Zabbix server time" but anything else (including value's timestamp)! Screenshots from the frontend and logs with debug level 5 from Zabbix server in attachments in archives (all IP addresses and credentials in screenshots and logs is hided.) Expected: A trigger must immediately be changing to an unsupported state after the item transitions to an unsupported state. Zabbix is Open Source and comes at no cost.
#Zabbix fuzzytime software#
0 - if difference between item timestamp value and Zabbix server timestamp is over T seconds 1 - otherwise. Zabbix is the ultimate enterprise-level software designed for real-time monitoring of millions of metrics collected from tens of thousands of servers, virtual machines and network devices. As result, it makes useless trigger expressions like "host:(SomeValue)" if this metric is collected by agent in active mode, as value and timestamp should be equal "by design" in this case.Īt the same time, documentation always has the following description for trigger function fuzzytime():Ĭhecking how much an item value (as timestamp) differs from the Zabbix server time. 'Supported trigger function' section in Zabbix Documentation 3.4 says following about fuzzytime: Checking how much an item timestamp value differs from the Zabbix server time.
The key moment is: the current value of item is compared with timestamp of this value. Cyclone in this comment describes how Zabbix server processes the fuzzytime() function at the moment.
0 kommentar(er)
