Hi Guys
We are looking to roll out Zabbix into our production environment but we have hit a couple of snags that we don't seem to be able to solve so thought it best to ask here to see if anyone has any experience with them.
First up we will be running 3.4.X purely containerised (Docker for Web, Server and Proxies) on a Docker swarm.
We want the containers to be totally stateless and be able to be automatically spun up in the event of failure, we don't seem to be able to find any way to inject the LDAP configuration into the container at the start using the documented environment variables. We have also had a look at the DB schema and don't seem to be able to locate anywhere we can "inject" the LDAP connection strings into the DB. Does anyone have any experience of this or offer any advice?
Second question - We have noticed that the Standard Windows Agent for Zabbix comes without TLS enabled, we are happy to compile our own (using Jenkins) but we could ideally use a list of packages and tools needed and we will then "roll our own" TLS enabled agent.
Thanks in advance
Steve
We are looking to roll out Zabbix into our production environment but we have hit a couple of snags that we don't seem to be able to solve so thought it best to ask here to see if anyone has any experience with them.
First up we will be running 3.4.X purely containerised (Docker for Web, Server and Proxies) on a Docker swarm.
We want the containers to be totally stateless and be able to be automatically spun up in the event of failure, we don't seem to be able to find any way to inject the LDAP configuration into the container at the start using the documented environment variables. We have also had a look at the DB schema and don't seem to be able to locate anywhere we can "inject" the LDAP connection strings into the DB. Does anyone have any experience of this or offer any advice?
Second question - We have noticed that the Standard Windows Agent for Zabbix comes without TLS enabled, we are happy to compile our own (using Jenkins) but we could ideally use a list of packages and tools needed and we will then "roll our own" TLS enabled agent.
Thanks in advance
Steve