. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 Example API session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . mbstring check may fail with PHP < 5.2 in Zabbix 1.8. To avoid this issue, copy zabbix.conf.php.example file to zabbix.conf.php and modify parameters, including database access parameters. • For IPMI includes both visual and functional improvements, like the time period selector already mentioned. For example, information about max/min/avg values is presented clearly as a table. 12 2.4.1 Improved timeline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 3 Setup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 4 VMware monitoring setup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 11 Maintenance necessity to create multiple similar user scripts with only a single parameter difference. For example, you may want to supply a different integer or a different URL address to the script during execution

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 3 Setup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 4 VMware monitoring setup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 11 Maintenance problems The new version comes with an option to mark problems as cause or symptom problems. For example, power outage may be the actual root cause why some host is unreachable or some service is down.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 4 Setup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . supports three different modes for counting all changes, only decreases, or only increases. As an example, it can be used to track changes in the number of users or the number of system uptime decreases matching type of information, if selected item key returns data only of the specific type (for example, log[] item requires Type of information: Log). Type of information parameter is now located under

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 4 Setup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . availability is counted towards the total agent availability in the same way as a passive interface is, for example: • if a passive agent interface is available, and active checks are available - the total availability formatting change has been implemented to simplify further processing of the returned JSON (for example, in preprocessing steps or LLD macros). Tag reading from VMware VMware items reporting various

implemented into JavaScript engine. It will allow to pause JavaScript execution if required. For example, it may be useful in webhooks when working with two separate services, which have a delay between correlation - a method of correlating problems to their resolution flexibly and precisely. For example, you may define that a problem reported by one trigger may be resolved by another trigger, which Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the

comparison is now allowed in triggers, using the = (equal) and <> (not equal) operators. So, for example, it is now possible to define triggers that create alarm if the strings returned by two items are Some frontend sections in Zabbix may display a different page depending on user selection. For example, Administration → General may display twelve different pages. Previously, the page selection was change allows to de-clutter the interface of having to configure too many options in one screen. For example, details of an action operation are now opened in a separate popup window. New filtering options

may be a need to retrieve a new value quicker - to pick up changes in discoverable resources, for example. This is now made possible in the new Zabbix version by means of a Check now button that is available macros, allowing to extract a certain part of the macro value using a regular expression. For example, you may want to extract the customer name and interface number from the following LLD macro for frontend pages In the new Kiosk mode for frontend pages only the page content is displayed. Thus, for example, in dashboards only the widgets are displayed. |<| |<| |-| |<| Kiosk mode is accessible by clicking

for period Note that the new functions return a result based on trend values, not history. For example, you may want to know if there was a significant increase of server load last month (a 10% increase the new ”Event name” parameter in trigger configuration to build a meaningful alert message, for example to receive something like: "Load of Exchange server increased by 24% in July (0.69) comparing to build this message. For more details on configuring the event name, see a trigger configuration example. See also: • Supported trigger functions • Trigger configuration • Macro functions • Supported

These macros can be used to create item prototypes using the new systemd.unit.info[] item key, for example systemd.unit.info["{#UNIT.NAME}",LoadState]. See also: • Discovery of systemd services • Zabbix therefore can return values without the limitations associated with LLD macro name generation (for example, hyphens, square brackets and non-ASCII characters): jmx.get[,] The of these triggers does not reference the host or item, but only the function ({last()}<>0 in the example): Host ... Item item.key