[ZBXNEXT-4393] Add individual item recchock option when unsupported Created: 2018 Feb 21 Updated: 2018 Feb 22 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Agent (G), Frontend (F), Proxy (P), Server (S) |
Affects Version/s: | 3.4.7, 3.4.8rc1, 4.0.0alpha3 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Major |
Reporter: | Diego Narducci Arioza | Assignee: | Zabbix Support Team |
Resolution: | Unresolved | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
All |
Description |
You can implement an option to manually configure each trigger when it is not supported, in many cases, we use the nodata function to check if a bank instance is ok or not, when the instance drops the item gets error and has to wait for the zabbix global retraction time, when you need to leave this value high, the item in this example even after being solved very fast will have to wait zabbix global temple for rechecation, I think it would be very interesting to put an individual option in cad aitem for rechecagem if it is not supported. |
Comments |
Comment by richlv [ 2018 Feb 21 ] |
while unsupported items should work with nodata() in recent releases, could this issue be a duplicate of https://support.zabbix.com/browse/ZBXNEXT-473 ? |