[ZBXNEXT-540] ZBX_NOTSUPPORTED from external scripts Created: 2010 Oct 21  Updated: 2018 Feb 07

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Agent (G)
Affects Version/s: 1.8.4
Fix Version/s: None

Type: New Feature Request Priority: Major
Reporter: Marcel Hecko Assignee: Unassigned
Resolution: Unresolved Votes: 6
Labels: documentation, exitcodes, externalchecks, notsupported
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBXNEXT-1897 Return unknown (unsupported) value by... Closed
is duplicated by ZBXNEXT-2110 Empty string is valid return value Closed

 Description   

The zabbix agent native interface provides information whether the key is being supported or not outputting ZBX_NOTSUPOPRTED string to the zabbix server, which then reacts to the information and temporarily disables the key check for that particular host.

This funcionality does not seem to be implemented for external checks - keys calling external scripts in externalscripts directory. This is a very nice to have feature. We do have Oracle, Weblogic and LUSTRE fs monitoring implemented in Zabbix, however we would really appreciate to have this feature enabled in zabbix server.



 Comments   
Comment by Aleksandrs Saveljevs [ 2010 Oct 22 ]

As a workaround, you can make the script output nothing - in that case the external check will be treated as not supported.

Comment by Marcel Hecko [ 2010 Oct 22 ]

Great indeed! There is a secion in Zabbix documentation thought, that script should NEVER output nothing. This might be changed as this is a very important information In my case this solves the issue, however ZBX_UNSUPPORTED output recognition would be a benefit in zabbix monitoring infrastructure consistency. Thanks for a great work!

Comment by Alexei Vladishev [ 2012 Oct 11 ]

I believe it should be documented and closed.

Comment by richlv [ 2014 Mar 13 ]

for the record, external checks and userparams now may return empty values so this workaround probably will not help anymore

Comment by richlv [ 2015 Mar 13 ]

a patch suggestion at ZBXNEXT-2110

Comment by Filipp Sudanov (Inactive) [ 2015 Mar 13 ]

Similar for user parameters: ZBXNEXT-152

Comment by Glebs Ivanovskis (Inactive) [ 2017 Nov 09 ]

Exit code check was implemented in ZBXNEXT-1380, but was then reverted in ZBX-12594.

This piece of information may be of some interest for watchers.

Generated at Thu May 02 00:44:38 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.