Current drawbacks with 1.1beta10

[timo]

This thread includes topics which I encountered while testing out a new project with zabbix as backend. I will most likely contribute solutions to get around this.

- Key length is limited to 64 characters.

This results in some problems with custom items, e.g. UserParameter=Basic.URL[*],/home/zabbix/customchecks/urlcheck.sh $1 doesn't work as $1 is being stripped out

- Server side checks

Currently, there is no way to run items on the server (e.g. to monitor foreign servers). Only scripts on the clients running the zabbix agent are working.

[sauron]

- Server side checks

Currently, there is no way to run items on the server (e.g. to monitor foreign servers). Only scripts on the clients running the zabbix agent are working.

Use zabbix_sender on server and zabbix_trapper on server. I'm use this for monitor APC UPS.

[timo]

Use zabbix_sender on server and zabbix_trapper on server. I'm use this for monitor APC UPS.

Yes, it's a good way for monitoring an UPS device. But if you have a scenario where the items are remotely checked, but need to belong to the server/host itself, this is not that good.

One example which comes into my mind is the measuring of availability via remote checks (e.g. if a specific URL can be fetched within a specific deadline) must be run on the zabbix server itself, but the data needs to show up at the hosts to be checked.