It'd be really nice if the default zabbix_agent.conf was actually split apart into a few pieces as shipped: a generic section that one might expect would apply to most (linux, in this case) hosts; a UserParameter section; and a host-specific section (which would hold Server=, ServerPort=, Hostname=, and ListenIP=). Doing this would make it a lot easier to update (for instance) the list of UserParameters (like when a new app is installed), and just scp it to the affected machines without worrying about editing the Hostname=.
-
-
You may use Include= in order to include any external configuration files to the existing configuration. The external configuration file may contain, for example, list of user parameters for easy maintenance. -
Alexei, my only point is that Zabbix should be *distributed* with an include=userparms.conf and a separate (example) userparms.conf.
I have had to split up (after the fact, dammit!) almost 100 zabbix_agentd.conf files once we had the need to do our own userparameters. I would hate for anyone else on earth to have to go through that pain *after* they've deployed Zabbix.
Number of hosts (monitored/not monitored/templates/deleted) 158(125/0/33/0)
Number of items (monitored/disabled/not supported)[trapper] 12684(10698/155/1831)[0]
Number of triggers (enabled/disabled)[true/unknown/false] 5568(5096/472)[4/1181/3911]Comment
-
Comment
Comment