[ZBXNEXT-2798] New/extended item key - count of problem triggers. Created: 2015 Apr 23  Updated: 2020 Aug 04

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 2.4.2
Fix Version/s: None

Type: Change Request Priority: Minor
Reporter: Matthew Daize Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: newitemkey, state, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian


 Description   

Use Case:
Track count of problem triggers of different severities over a period of time.

Ideal Operation:
The administrator should be able to create an item with "zabbix[triggers]" but with parameters to specify current state and/or priority.

Benefit:
This allows organizations to be able to track over a period of time their responsiveness to triggers as a whole.

Workaround:
The administrator must write an script which grabs the count of the triggers via API in specific state then apply it to an item via external check.

 Comments   
Comment by Simon Begin [ 2020 Aug 04 ]

All this info is already available in the "Problem by Severity" widget of the Dashboard. However it's not available elsewhere except by creating an external script.

Having this info locally could be useful to trigger a higher priority notification when there are multiple problems for some criteria. For example advising supervisors when more than 10 hosts are critical. This is also unachievable with Escalations.

Generated at Tue Jul 08 09:49:04 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.