zabbix_sender as daemon

[cooper]

it seems like it would be fairly easy to make all of the items supported by agent[d] availiable to sender[d]. Or, to put it another way run zabbix_sender as a daemon, with a config file that had the items you wanted to check. I am thinking something like this

zabbix_sender.conf

zabbix_trapper_host my.zabbix.server
port 10001

## Items monitored on this host
## item time_interval (in minutes)
diskfree[/var] 60
system[procload] 5
system[procload5] 5
system[procload15] 5

This way the program is daemonized and you dont have to call it from cron. And all of these items are already availble to agent[d], so you wouldnt have to come up with a shell script to awk | cut | tail | grep | a commands output to send it back to the trapper[d] server.

I love the Zabbix product, I just like the idea of the hosts sending back to the server, rather than the server polling the host.

thanks for all your work alexi.

cooper

[Alexei]

I love the Zabbix product, I just like the idea of the hosts sending back to the server, rather than the server polling the host.

I will try to explain briefly what major disadvantages I see in this model:

1. Lack of centralised configuration.
2. Handling of situations when ZABBIX server is unreachable

Of course, we can rid of 1. by sending configuration from the server. It would require adding lots of logic to both the server and agents.

Anyway, I see nothing wrong in this approach. It is very possible that it will be implemented at some point.

If you want to implement it now, I would suggest the following:

1. Run zabbix_agent(d) on host being monitored
2. Write Perl or C program that would run on the host and retrieve data from the agent by connecting to 127.0.0.1:10000 (be default) and send it to ZABBIX server
3. The script or binary would use its own configuration file, thus no changes to neither zabbix_sender nor zabbix_agent(d) required

I hope this helps.

[cooper]

1. Run zabbix_agent(d) on host being monitored
2. Write Perl or C program that would run on the host and retrieve data from the agent by connecting to 127.0.0.1:10000 (be default) and send it to ZABBIX server
3. The script or binary would use its own configuration file, thus no changes to neither zabbix_sender nor zabbix_agent(d) required

I hope this helps.

Alexi,
Thanks for your reply. I had thought of this as a solution. I will look into it further.

cooper

[doronta]

hi
about your suggestion that agent will send to the server ?

how the the agent can send something!! ?



thanks
doron