[ZBXNEXT-4388] Add filter by exact priority to triggers API Created: 2018 Feb 19 Updated: 2018 Feb 19 Resolved: 2018 Feb 19 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | API (A) |
| Affects Version/s: | 3.4.7, 4.0 (plan) |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Ilja Livenson | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Currently only filtering by min_priority is supported in Zabbix APIs. If we only need triggers of a certain type it means we have to filter them once the data is retrieved from Zabbix, which causes extra CPU/latency. Please add a filter to be able to define exact priority. Reference: https://www.zabbix.com/documentation/4.0/manual/api/reference/trigger/get |
| Comments |
| Comment by richlv [ 2018 Feb 19 ] |
|
"filter" object should allow that. try something like : "filter": { "priority": 3 } |
| Comment by Ilja Livenson [ 2018 Feb 19 ] |
|
Very cool, thanks! |