[ZBXNEXT-7601] More control to problem tags in services Created: 2022 Apr 04  Updated: 2024 Jun 27

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 6.0.2
Fix Version/s: None

Type: Change Request Priority: Medium
Reporter: Roni Väyrynen Assignee: Valdis Murzins
Resolution: Unresolved Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Current implementation of services offers very basic ways to match tags. In some cases this makes it very difficult to differentiate eq. simple ICMP ping triggers between different host groups using same template.

Currently problem tags offer only "equals" and "contains". I'd very much like to see following to make it consistent with so many other places:

 

  • besides the current options have: exists, does not exist, does not contain, does not equal. It would be even better if there was a way to match with regular expression.
  • make it more flexible with: and, or, and/or, custom expression


 Comments   
Comment by Rodrigo P [ 2022 Apr 07 ]

Excellent feature request.

Totally agree Zabbix needs to offer more operations for service problem tag conditions.

Comment by John Koyle [ 2024 Jun 27 ]

Completely agree... the default network templates using ICMP have added scope: availability to the ICMP response time trigger (along with scope: performance). Using problem tags (availability) in services, there's no way to exclude high ICMP responses from hitting SLA's). This is a simple use case that should be easy to solve.

Generated at Wed Jul 16 11:20:13 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.