[ZBXNEXT-5246] A new API for analyzing the zabbix queue Created: 2019 May 29 Updated: 2019 May 29 |
|
| Status: | Confirmed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | API (A) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Andrea Biscuola | Assignee: | Alexander Vladishev |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | api, debugging, usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
A lot of times, it happen that we need to analyze more than 500 items in the zabbix queue and the current page, is limiting when dealing with global scale issues. Working with the support, it happen that there is no standardized way and no defined knowledge/procedure, for how to extract, in a parseable form, which items, related to which hosts, are stuck in the queue. It would be nice if an API in the form "zabbix.queue" or "proxy.queue" could be provided, where the detail, of every single delayed item (itemid, hostid, key and name) can be fetched from the database without resorting to some magic, one shot, query. |
| Comments |
| Comment by Andrea Biscuola [ 2019 May 29 ] |
|
If required, I could help identifying eventual design needs for this. |