I'm in an environment where new machines are being set up, and then failing shortly thereafter somewhat quickly (a week+). That's all to be expected (believe it or not) but everytime a machine needs to be added, it's vaguely a chore to go add it to the zabbix config so I can watch it while it is running, and can know when it goes down and to replace it.
So, is there a hack somehow to make it so the first time a zabbix_agentd contacts the server with a new hostname, the server recognizes it's a new setup and either a) adds it to my config, under a template (possibly defined in the agentd.conf file on the monitored box), or b) notifies me next time i login to the server config that there's a new machine reporting to me (this could be it's own configuration page)
thoughts? like I said I'm willing to hack it up, just not sure how (or where) to trap for the hostnames, to see if it's one we're already monitoring, or one we want to add
So, is there a hack somehow to make it so the first time a zabbix_agentd contacts the server with a new hostname, the server recognizes it's a new setup and either a) adds it to my config, under a template (possibly defined in the agentd.conf file on the monitored box), or b) notifies me next time i login to the server config that there's a new machine reporting to me (this could be it's own configuration page)
thoughts? like I said I'm willing to hack it up, just not sure how (or where) to trap for the hostnames, to see if it's one we're already monitoring, or one we want to add
Comment