Unary - and not are non-associative (meaning -(-1) and not (not 1) should be used instead of -1 and not not 1). They also must be surrounded by spaces or parentheses.Īll operators, except unary - and not, have left-to-right associativity. ![]() Not, and and or operators are case-sensitive and must be in lowercase. (If the cast fails - numeric operand is cast to a string operand and both operands get compared as strings.) operator other than = or is used on an operand. ![]() The operator is defined as:ġ String operand is still cast to numeric if: Preceded by a hash mark, the parameter has a different meaning: You may use seconds or time suffixes to indicate time. ![]() Most of numeric functions accept time as a parameter. See the supported functions for a complete list of these parameters. Function-specific parametersįunction-specific parameters are placed after the item key and are separated from the item key by a comma. While other trigger expressions as function parameters are limited to non-history functions in triggers, this limitation does not apply in calculated items. The referenced item must be in a supported state (except for nodata() function, which is calculated for unsupported items as well). The host and item key can be specified as /host/key. other expressions (not available for functions referencing the host item history, see other expressions for examples).host and item key (functions referencing the host item history only).When returning strings, comparison is possible with the = and operators (see example). Typically functions return numeric values for comparison. Functionsįunctions allow to calculate the collected values (average, minimum, maximum, sum), find strings, reference current time and other factors.Ī complete list of supported functions is available. This is useful to create hysteresis and avoid trigger flapping. When defining both problem expression and the supplemental recovery expression, problem resolution becomes more complex: not only the problem expression has to be FALSE, but also the recovery expression has to be TRUE. As soon as the problem expression evaluates to FALSE, the problem is resolved. As soon as the problem expression evaluates to TRUE, there is a problem. When defining a problem expression alone, this expression will be used both as the problem threshold and the problem recovery threshold. recovery expression (optional) - defines additional conditions of the problem resolution.problem expression - defines the conditions of the problem.While the syntax is exactly the same, from the functional point of view there are two types of trigger expressions: Will trigger if the number of received bytes during the last five minutes was always over 100 kilobytes. This fact has been verified on test benches Zabbix Server 5.0.11 and 5.0.12 in the following environments: The documentation does not describe that this feature works in unsupported state. 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.)Ī trigger must immediately be changing to an unsupported state after the item transitions to an unsupported state. Recovering of the trigger from an unsupported state also occurs after the second successful acquisition of the value. Trigger will change to unsupported state after second unsupported check. This creates false problems with incorrect date and time. The trigger did not go into an unsupported state. Waiting for the next item check and changing of the item to an unsupported state.Simulate a problem with an item, such as changing the password to connect to the database.Get the first successful value without problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |