How does disabling custom param's work?

[edeus]

Hello,

I have the following UserParam:
areca[],/usr/local/bin/areca-info $1 $2

There are about 10 different values that are monitored. i.e. areca[1] through areca[10] each giving different information and monitored as seperate items of course.

As these go on and off, if they are off, zabbix does not need to continuously monitor it. The way it works is fine.

The problem I am having is because one of the areca[] values returns no data, Zabbix goes unsupported.

Does this sound correct or could there be another problem I am not seeing?

As a workaround I could change the `/usr/local/bin/areca-info` script to return 0 instead of nothing but this could also be a problem returning 0 possibly could also be an emergency event (temperature or complete failure).

[Alexei]

Yes, this sounds correct. Make sure that your script always returns something to get rid of the problem.

[KarmaPolice]

As a really cheesy workaround you can set your "Refresh Unsupported Items" to be less than your monitor interval as well... this should make it go back to a supported state everytime it goes out to check.

This option is in the Configuration > General > Other menu for 1.1b4 You'll have a lot of errors/events arise in your server log... but it shouldn't be a huge issue if you know that this is intended behavior.

[edeus]

Nice hack there :)

I opted to setting multiple static params. It seemed the best way forward.