Why no TEST ITEM button...

[roycruse]

It seems a really handy missing feature in Zabbix is a TEST ITEM button.

When configuring a new host and adding items to monitor there is no way to fire the item immediately and see any errors/debug returned.

This would make troubleshooting non working items a breeze.

Any chance this can be added ?

[ajhalls]

Love this idea, I was just posting about it in the troubleshooting forums.

[nick0909]

You can use zabbix_get or zabbix_sender to do this, it is more manual though.

[kloczek]

When configuring a new host and adding items to monitor there is no way to fire the item immediately and see any errors/debug returned.

This would make troubleshooting non working items a breeze.

Any chance this can be added ?

No because not immedade check item is consequence not of the zabbix architecture but exact settings across whole zabbix stack.

If you are using proxy and active monitoring agent is asking proxy/server for configuration every RefreshActiveChecks seconds which is 120s.
If agent is monitored over proxy active proxy is refreshing his configuration every ConfigFrequency which is 3600s (1h). In case of using passive proxy server by default pushes updated cfg data every CacheUpdateFrequency seconds (60s) by default.

[glebs.ivanovskis]

Consider voting for ZBXNEXT-473.

[kloczek]

In most interesting and/or high performance monitoring cases passive monitoring is useless. Simple it does not scale.
Have even few minutest delay between making change and possibility of checking results of the cfg changes is not big deal so please stop voting or demanding stupid things.

[ajhalls]

For me it would have been great as a new user to troubleshoot the issues of a fresh installation. Surely it isn't as big of a deal to a seasoned user, or an established installation, but it isn't a bad idea.

[kloczek]

For me it would have been great as a new user to troubleshoot the issues of a fresh installation. Surely it isn't as big of a deal to a seasoned user, or an established installation, but it isn't a bad idea.

Seems you still do not understand that what you are asking would require very deep zabbix architecture changes which would not bring to much if completely nothing to other possibilities.

If you are just start building new monitoring stack just change server/proxy/agents settings to have more frequent cfg updates. In my biggest monitoring stack I had 1min delay between apply change and full propagation of it on scale almost 300k items with about 3knvps. It is not a rocket science.
Again: to have short delay you don't need to ask to have any zabbix code changes. All what you need is set of proper settings across whole stack. In other words this conversation is pointless as seems expectation here is to have something automagically/OOTB.