64bit systems with glibc versions older than 2.5. Common symptom is failing to start with the error message: Floating point exception. Use older versions, or compile from the scratch on the target system and error text is available in a popup. Clicking the icon opens the popup to allow copying of the message. 2.11.2 History strings saved by reference At the top of the frontend, there’s a breadcrumbs type notifications involve both showing a message and playing a sound. Global notifications can be enabled per user in profile configuration. If enabled, global message timeout can be changed. By default,

monitoring of WEB applications from various geographical locations. Also new items ”Last error message of scenario ’$1’” with key web.test.error[] will be added to all existing scenarios frontend in Administration → Scripts can now display a confirmation message before being executed. A custom message confirmation message can be entered by the administrator. This feature should be especially = PROBLEM” is added to new actions, so only problem notifications are sent. This makes recovery message checkbox operate in a more intuitive way. This action condition can be removed by the user. 5.5

difference is clear by seeing the media type used. Also, when displaying a system user that the message is sent to, the name and surname of the user (as configured in user configuration) is displayed indicate the reason to the user. Since Zabbix 2.2.0, after adding 7 flexible intervals to an item, the message ”Maximum number of flexible intervals added” is shown: Send to field length in user media properties sec] 27 zabbix22 4674 4670 0 14:55 ? 00:00:00 zabbix_proxy: heartbeat sender [sending heartbeat message success in 0.013643 sec, idle 30 sec] zabbix22 4688 4670 0 14:55 ? 00:00:00 zabbix_proxy: icmp pinger

nodata() function fails due to lack of data on the server, a more informative message is displayed. Previous vague message of Evaluation failed for function... has been expanded to include item does not Any problem in the config file is checked for and reported before writing to the logfile. Error message is printed in the terminal window now. zabbix_agentd no longer requires a configuration file to error message for passive agents will not be visible in the frontend. Querying values with zabbix_get, testing with zabbix_agentd -p and zabbix_agentd -t now also provides a detailed error message. As

easier in Zabbix. If previously there was the slightly confusing concept of a special ”Recovery message” or the possibility to create a full escalation when problem triggers go OK, now that has been united (instead of making such items that will inevitably fail on later stages). A corresponding error message will be displayed in Configuration → Hosts → Discovery. 7.5 Item changes 7.5.1 VMware monitoring LDAP configuration form is hidden in Administration → Authentication and a corresponding error message is displayed. 12.2 Daemon improvements 13 What’s new in Zabbix 3.2.8 Frontend improvements •

versions three hard-coded parameters were passed to custom alert scripts - Send to, Subject and Message. Now users can define their own command-line parameters for the script in the media type configuration supported in parameter fields - {ALERT.SENDTO}, {ALERT.SUBJECT} and {ALERT.MESSAGE}, resolving to recipient, message subject and message body respectively. For more details, see: • Custom alertscripts • acknowledged. That imposed certain limitations, for example, you could not add a second acknowledgement message as all events were deemed acknowledged. In Zabbix 3.0 you have more flexible options when using

will be ”0”; otherwise, the component will exit with non-zero exit code and a corresponding error message. Warnings (e.g., in case of a deprecated parameter) will not affect successful exit code. Stream either to discard the value, set a specified value or set a specified error message. 13 It is now possible to match the error message to a regular expression. If the error matches (or does not match) it is is possible to specify how the error case should be processed. For example, a specific error message can be ”mapped” to a more general case to be matched for and handled by a further preprocessing step

notification recipients, now you can also filter records by actions, media types, status, or by the message/remote command content. These filtering options can also be configured for the Action log widget commands. 24 media - a means of delivering notifications; delivery channel. notification - a message about some event sent to a user via the chosen media channel. remote command - a pre-defined command case Zabbix provides mutexes for locking in OpenSSL. If a mutex lock or unlock fails then an error message is printed to the standard error stream (STDERR) and Agent 2 exits with return code 2 or 3, respectively

NAME} macro • Problem notifications have been made more distinct from recovery notifications in the message subject 7 Item value preprocessing When it comes to preprocessing item values before storing them days to 1 day. • Maximum error message length has been increased from 128 to 2048 symbols for trigger and alert errors. This should reduce the possibility of error message being trimmed. Error messages thread crashes Previously, in case of a Zabbix agent metric thread crash only a one-line error message was logged. Now additional information including the program counter, register, stack frame (only

replace them with some default value or simply replace them with a human-readable error message. Extracting an error message provided in incoming data is another new feature. For example, a JSON object may contain ”error”. If the field exists preprocessing is able to extract its value and set it as an error message for the item. 8 Throttling rules allow to process value only if it is changed, thus reducing the handling option, e.g.: • discard the value • set to a specified value • set a specified error message Testing preprocessing steps As new item preprocessing steps are being added the preprocessing pipeline