[ZBXNEXT-3544] retrieving item values upon events Created: 2016 Nov 12  Updated: 2018 Sep 12

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: 3.2.1
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: richlv Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: duplicates, items
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PDF File Advanced preprocessing 1.0rc1.pdf    
Issue Links:
Causes
causes ZBXNEXT-4724 Advanced preprocessing: validation an... Closed

 Description   

zabbix items normally are polled at some interval. while this is ok for many metrics, for some it might make more sense to poll them less frequently.

for example, a system might have a static number of cores, max memory size and a few other parameters (some systems have these dynamic, our hypothetical system not ).
it doesn't make much sense polling these hourly. polling them weekly is a bit better, but if it changes after a reboot, it will take up to a week for zabbix to notice the change.

it would be nice to have some way to tell "poll this item only upon some condition".
for active agent items, it could be agent startup - but that wouldn't work that well with other items (like checking max memory size over snmp).

maybe a way to tie item polling to a trigger firing ? that way a "system freshly booted" trigger could make a bunch of items collect data, and we would not keep on collecting static data again and again.



 Comments   
Comment by Oleksii Zagorskyi [ 2016 Nov 14 ]

A bit similar to ZBXNEXT-1846

Comment by Alexei Vladishev [ 2018 Aug 20 ]

Hey all! Please have a look at the attached acceptance criteria document that describes proposed enhancements for preprocessing that will cover this functionality as well as ZBXNEXT-1846 and ZBXNEXT-4016. It has all chances to be implemented in Zabbix 4.2. Let me know what you think. Is there anything to improve? I appreciate any feedback.

Generated at Fri Mar 29 16:25:03 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.