2 Problems

Overview

Operational data of problems

It is possible to display operational data for current problems, i.e. the latest item values as opposed to the item values at the time of the problem.

Operational data display can be configured in the filter of Monitoring → Problems or in the configuration of the respective dashboard widget, by selecting one of the three options:

• None - no operational data is displayed

• With problem name - operational data is appended to the problem name and in parentheses. Operational data are appended to the problem name only if the Operational data field is non-empty in the trigger configuration.

The content of operational data can be configured with each , in the Operational data field. This field accepts an arbitrary string with macros, most importantly, the macro.

{ITEM.LASTVALUE<1-9>} in this field will always resolve to the latest values of items in the trigger expression. {ITEM.VALUE<1-9>} in this field will resolve to the item values at the moment of trigger status change (i.e. change into problem, change into OK, being closed manually by a user or being closed by correlation).

Negative problem duration

It is actually possible in some common situations to have negative problem duration i.e. when the problem resolution time is earlier than problem creation time, e. g.:

• If some host is monitored by proxy and a network error happens, leading to no data received from the proxy for a while, the nodata(/host/key) trigger will be fired by the server. When the connection is restored, the server will receive item data from the proxy having a time from the past. Then, the nodata(/host/key) problem will be resolved and it will have a negative problem duration;
• When item data that resolve the problem event are sent by Zabbix sender and contain a timestamp earlier than the problem creation time, a negative problem duration will also be displayed.

Negative problem duration is not affecting or Availability report of a particular trigger in any way; it neither reduces nor expands problem time.

Mass editing options

• Mass update - update the selected problems by navigating to the problem update screen

To use this option, mark the checkboxes before the respective problems, then click on the Mass update button.

Buttons

The button to the right offers the following option:

View mode buttons, being common for all sections, are described on the Monitoring page.

Using filter

You can use the filter to display only the problems you are interested in. For better search performance, data is searched with macros unresolved.

The filter is located above the table. Favorite filter settings can be saved as tabs and then quickly accessed by clicking on the tabs above the filter.

Tabs for favorite filters

Frequently used sets of filter parameters can be saved in tabs.

To save a new set of filter parameters, open the main tab, and configure the filter settings, then press the Save as button. In a new popup window, define Filter properties.

Notes:

• To hide a filter, press on the name of the current tab. Press on the active tab name again to open the filter.
• Filter tabs can be re-arranged by dragging and dropping.
• Keyboard navigation is supported: use arrows to switch between tabs, press Enter to open.
• Pressing the arrow down icon in the upper right corner will open the full list of saved filter tabs as a drop-down menu.

To share filters, copy and send to others a URL of an active filter. After opening this URL, other users will be able to save this set of parameters as a permanent filter in their Zabbix account.
See also: Page parameters.

Filter buttons

Event menu

Clicking on the problem name brings up the event menu:

The event menu allows to:

• filter the problems of the trigger
• access the trigger configuration
• access a simple graph/item history of the underlying item(s)
• execute global (these scripts need to have their scope defined as ‘Manual event action’). This feature may be handy for running scripts used for managing problem tickets in external systems.

Viewing details

The times for problem start and recovery in Monitoring → Problems are links. Clicking on them opens more details of the event.

Note how the problem severity differs for the trigger and the problem event - for the problem event it has been updated using the Update problem .

• - problem event generated
• - message has been sent
• - problem event acknowledged
• - problem event unacknowledged
• - a comment has been added
• - problem severity has been increased (e.g. Information → Warning)
• - problem severity has been decreased (e.g. Warning → Information)
• - problem severity has been changed, but returned to the original level (e.g. Warning → Information → Warning)
• - a remote command has been executed
• - problem event has recovered