There is an option to define custom event tags in Zabbix. Event tags are defined on the trigger level. After the tags are defined, corresponding new events get marked with tag data.
Having custom event tags allows for more flexibility. Most importantly, events can be correlated based on event tags. In other uses, actions can be defined based on event tags.
Event tags are realized as a pair of the tag name and value. You can use only the name or pair it with a value:
Some use cases for this functionality are as follows:
* Define tags in the log trigger that will identify events using value extraction by the {{ITEM.VALUE<N>}.regsub()} macro;
* In trigger configuration, have multiple problem event generation mode;
* In trigger configuration, use [[:manual/config/event_correlation|event correlation]]: select the option that OK event closes only matching events and choose the tag for matching;
* See problem events created with a tag and closed individually.
- Use it to filter notifications
* Define tags on the trigger level to mark events by different tags;
* Use tag filtering in action conditions to receive notifications only on the events that match tag data.
- See event tag information in the frontend
* Define tags on the trigger level to mark events by different tags;
* See this information in //Monitoring// → //Problems//.
- Use information extracted from item value as tag value
* Use an {{ITEM.VALUE<N>}.regsub()} macro in the tag value;
* See tag values in //Monitoring// → //Problems// as extracted data from item value.
- Identify problems better in notifications
* Define tags on the trigger level;
* Use an {EVENT.TAGS} macro in the problem notification;
* Easier identify which application/service the notification belongs to.
- Simplify configuration tasks by using tags on the template level
* Define tags on the template trigger level;
* See these tags on all triggers created from template triggers.
- Create triggers with tags from low-level discovery (LLD)
* Define tags on trigger prototypes;
* Use LLD macros in the tag name or value;
* See these tags on all triggers created from trigger prototypes.
Event tags are defined in trigger configuration. Event tags can be defined for triggers, template triggers and trigger prototypes.
The following macros may be used in event tags:
{EVENT.TAGS} and {EVENT.RECOVERY.TAGS} macros can be used in trigger-based notifications and they will resolve to a comma separated list of event tags or recovery event tags.
Substring extraction is supported for populating the tag name or tag value, using a macro function - applying a regular expression to the value obtained by the {ITEM.VALUE}, {ITEM.LASTVALUE} macro or a low-level discovery macro. For example:
{{ITEM.VALUE}.regsub(pattern, output)}
{{ITEM.VALUE}.iregsub(pattern, output)}
{{#LLDMACRO}.regsub(pattern, output)}
{{#LLDMACRO}.iregsub(pattern, output)}
Tag name and value will be cut to 255 characters if their length exceeds 255 characters after macro resolution.
See also: Using macro functions in low-level discovery macros for event tagging.
Event tags, if defined, can be seen with new events in:
Only the first three tag entries are displayed. If there are more than three tag entries, it is indicated by three dots. If you roll your mouse over these three dots, all tag entries are displayed in a pop-up window.
Note that the order in which tags are displayed is affected by tag filtering and the Tag display priority option in the filter of Monitoring → Problems or the Problems dashboard widget.
可以选择在Zabbix中定义自定义事件标签。 事件标签在触发器级别定义。定义标签后,相应的新事件将被标签数据标记。 拥有自定义事件标签可以提供更大的灵活性。最重要的是,事件可以是基于事件标签的correlated。此外,可以基于事件标签来定义动作。 事件标签通过一对tag name 和 value实现。您只能使用名称或将其与值配对: MySQL, 服务:MySQL, 服务, 服务:客户, 应用, 应用:Java, 优先级:高
此功能的一些用例如下:
可以在事件标签中使用以下宏:
{EVENT.TAGS}和{EVENT.RECOVERY.TAGS}宏可用于基于触发器的通知,它们将解析为逗号分隔的事件标签或恢复事件标签列表。
使用宏 function支持子串提取以填充标签名称或标签值 - 将正则表达式应用于{ITEM.VALUE}, {ITEM.LASTVALUE}宏或低级发现宏。 例如:
{{ITEM.VALUE}.regsub(pattern, output)}
{{ITEM.VALUE}.iregsub(pattern, output)}
{{#LLDMACRO}.regsub(pattern, output)}
{{#LLDMACRO}.iregsub(pattern, output)}
如果使用宏后长度超过255个字符,则标签名称和值将被剪切为255个字符。 同样可查看:在low-level discovery macros中使用宏函数作为事件标签。
事件标记(如果已定义)可以在以下新事件中看到:
仅显示前三个标签条目。 如果有三个以上的标签条目,则用三个点表示。 如果将鼠标悬停在这三个点上,则所有标记条目都会显示在弹出窗口中。 请注意,标签显示的顺序受标签过滤和监控中 - > 问题或问题仪表板小组件过滤器中的标签显示优先级选项的影响。