[ZBXNEXT-4426] Check now item value without config reload Created: 2018 Feb 15 Updated: 2024 Apr 10 Resolved: 2018 Mar 28 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | None |
Fix Version/s: | 4.0.0alpha5, 4.0 (plan) |
Type: | New Feature Request | Priority: | Major |
Reporter: | Rostislav Palivoda | Assignee: | Andris Zeila |
Resolution: | Fixed | Votes: | 3 |
Labels: | None | ||
Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
Issue Links: |
|
||||||||||||
Sub-Tasks: |
|
||||||||||||
Team: | Team A | ||||||||||||
Team: | Team A | ||||||||||||
Sprint: | Sprint 27, Sprint 28, Sprint 29, Sprint 30 | ||||||||||||
Story Points: | 2 |
Comments |
Comment by Vladislavs Sokurenko [ 2018 Mar 15 ] |
Server side successfully tested. |
Comment by Andris Zeila [ 2018 Mar 15 ] |
Released in:
|
Comment by Marc [ 2018 Mar 16 ] |
What's the difference to |
Comment by Andris Zeila [ 2018 Mar 16 ] |
No configuration cache synchronization or waiting for it. So if you create an item and press check now - nothing happens. |
Comment by richlv [ 2018 Mar 17 ] |
|
Comment by Andris Zeila [ 2018 Mar 19 ] |
Maybe not, but it was implied. The normal use case would be creating/editing item, pressing 'check now' and expecting the new changes to be processed. Without it the feature is somewhat confusing and really limited. |
Comment by Marc [ 2018 Mar 19 ] |
To me the main use cases are firstly triggering a re-check of an unsupported item or LLD rule and secondly triggering a re-check when analyzing data. E.g. when the regular update interval is quite long or something just has been changed and one wants to investigate a potential effect quickly. In my opinion an on-demand or implicit configuration cache reload is nice to have too but negligible in comparison. |
Comment by Dimitri Bellini [ 2018 Mar 29 ] |
Dear guys, |
Comment by Marc [ 2018 Apr 10 ] |
I'd argue this is something that should not be available to every Zabbix user, as it may easily put Zabbix (or a monitored interface) to its knees. If made available to Zabbix users, then I'd very much appreciate a control mechanism, possibly on User group level as it is for instance currently the case with the Debug mode. |
Comment by richlv [ 2019 Mar 10 ] |
Marc, limits on this functionality would probably be a new feature request, given that this feature arrived in 4.0. |