<p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
<p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
<p>For more information and related downloads for Zabbix components, please visit <ahref="https://hub.docker.com/u/zabbix/">https://hub.docker.com/u/zabbix/</a> and <ahref="https://zabbix.com">https://zabbix.com</a></p>
<h1id="what-is-zabbix-proxy-">What is Zabbix proxy?</h1>
<p>Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.</p>
</code></pre><p>Where <code>some-zabbix-proxy-sqlite3</code> is the name you want to assign to your container, <code>some-hostname</code> is the hostname, it is Hostname parameter in Zabbix proxy configuration file, <code>some-zabbix-server</code> is IP or DNS name of Zabbix server and <code>tag</code> is the tag specifying the version you want.</p>
<blockquote>
<p>[!NOTE]
Zabbix server has possibility to execute <code>fping</code> utility to perform ICMP checks. When containers are running in rootless mode or with specific restrictions environment, you may face errors related to fping:
<code>fping: Operation not permitted</code>
or
lost all packets to all resources
in this case add <code>--cap-add=net_raw</code> to <code>docker run</code> or <code>podman run</code> commands.
Additionally fping executing in non-root environments can require sysctl modification:
<code>net.ipv4.ping_group_range=0 1995</code>
where 1995 is <code>zabbix</code> GID.</p>
</blockquote>
<h2id="connects-from-zabbix-server-passive-proxy-">Connects from Zabbix server (Passive proxy)</h2>
<p>This image exposes the standard Zabbix proxy port (10051) and can operate as Passive proxy in case <code>ZBX_PROXYMODE</code> = <code>1</code>. Start Zabbix server container like this in order to link it to the Zabbix proxy container:</p>
<h2id="connect-to-zabbix-server-active-proxy-">Connect to Zabbix server (Active proxy)</h2>
<p>This image can operate as Active proxy (<code>default</code> mode). Start your application container like this in order to link Zabbix proxy to Zabbix server containters:</p>
<h2id="container-shell-access-and-viewing-zabbix-proxy-logs">Container shell access and viewing Zabbix proxy logs</h2>
<p>The <code>podman exec</code> command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your <code>zabbix-proxy-sqlite3</code> container:</p>
<p>When you start the <code>zabbix-proxy-sqlite3</code> image, you can adjust the configuration of the Zabbix proxy by passing one or more environment variables on the <code>podman run</code> command line.</p>
<p>The variable allows to switch Zabbix proxy mode. Bu default, value is <code>0</code> - active proxy. Allowed values are <code>0</code> - active proxy and <code>1</code> - passive proxy.</p>
<p>This variable is unique, case sensitive hostname. By default, value is <code>zabbix-proxy-sqlite3</code> of the container. It is <code>Hostname</code> parameter in <code>zabbix_proxy.conf</code>.</p>
<p>This variable is IP or DNS name of Zabbix server or Zabbix proxy. By default, value is <code>zabbix-server</code>. It is <code>Server</code> parameter in <code>zabbix_proxy.conf</code>. It is allowed to specify Zabbix server or Zabbix proxy port number using <code>ZBX_SERVER_PORT</code> variable. It make sense in case of non-default port for active checks.</p>
<p>This variable is port Zabbix server listening on. By default, value is <code>10051</code>.</p>
<p><strong>Note:</strong> This parameter is no longer used in version 6.0 and above. Instead, add a colon <code>:</code> followed by the port number to the end of <code>ZBX_SERVER_HOST</code>.</p>
<p>The variable is list of comma separated loadable Zabbix modules. It works with volume <code>/var/lib/zabbix/modules</code>. The syntax of the variable is <code>dummy1.so,dummy2.so</code>.</p>
<p>The variable is used to specify debug level. By default, value is <code>3</code>. It is <code>DebugLevel</code> parameter in <code>zabbix_server.conf</code>. Allowed values are listed below:</p>
<ul>
<li><code>0</code> - basic information about starting and stopping of Zabbix processes;</li>
<li><code>1</code> - critical information</li>
<li><code>2</code> - error information</li>
<li><code>3</code> - warnings</li>
<li><code>4</code> - for debugging (produces lots of information)</li>
<li><code>5</code> - extended debugging (produces even more information)</li>
<p>The variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is <code>false</code>.</p>
<h3id="other-variables">Other variables</h3>
<p>Additionally the image allows to specify many other environment variables listed below:</p>
<pre><code><spanclass="hljs-attr">ZBX_ENABLEREMOTECOMMANDS</span>=<spanclass="hljs-number">0</span> # Available since <spanclass="hljs-number">3.4</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_LOGREMOTECOMMANDS</span>=<spanclass="hljs-number">0</span> # Available since <spanclass="hljs-number">3.4</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_PROXYHEARTBEATFREQUENCY</span>=<spanclass="hljs-number">60</span> # Deprecated since <spanclass="hljs-number">6.4</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_CONFIGFREQUENCY</span>=<spanclass="hljs-number">3600</span> # Deprecated since <spanclass="hljs-number">6.4</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_PROXYCONFIGFREQUENCY</span>=<spanclass="hljs-number">10</span> # Available since <spanclass="hljs-number">6.4</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_STARTPREPROCESSORS</span>=<spanclass="hljs-number">3</span> # Available since <spanclass="hljs-number">4.2</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_STARTHISTORYPOLLERS</span>=<spanclass="hljs-number">1</span> # Available since <spanclass="hljs-number">5.4</span>.<spanclass="hljs-number">0</span> till <spanclass="hljs-number">6.0</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_STARTODBCPOLLERS</span>=<spanclass="hljs-number">1</span> # Available since <spanclass="hljs-number">6.0</span>.<spanclass="hljs-number">0</span>
<spanclass="hljs-attr">ZBX_TLSCIPHERALL</span>= # Available since <spanclass="hljs-number">4.4</span>.<spanclass="hljs-number">7</span>
<spanclass="hljs-attr">ZBX_TLSCIPHERALL13</span>= # Available since <spanclass="hljs-number">4.4</span>.<spanclass="hljs-number">7</span>
<spanclass="hljs-attr">ZBX_TLSCIPHERCERT</span>= # Available since <spanclass="hljs-number">4.4</span>.<spanclass="hljs-number">7</span>
<spanclass="hljs-attr">ZBX_TLSCIPHERCERT13</span>= # Available since <spanclass="hljs-number">4.4</span>.<spanclass="hljs-number">7</span>
<spanclass="hljs-attr">ZBX_TLSCIPHERPSK</span>= # Available since <spanclass="hljs-number">4.4</span>.<spanclass="hljs-number">7</span>
<spanclass="hljs-attr">ZBX_TLSCIPHERPSK13</span>= # Available since <spanclass="hljs-number">4.4</span>.<spanclass="hljs-number">7</span>
</code></pre><p>Default values of these variables are specified after equal sign.</p>
<p>The allowed variables are identical of parameters in official <code>zabbix_proxy.conf</code>. For example, <code>ZBX_LOGSLOWQUERIES</code> = <code>LogSlowQueries</code>.</p>
<p>Please use official documentation for <ahref="https://www.zabbix.com/documentation/5.0/manual/appendix/config/zabbix_proxy"><code>zabbix_proxy.conf</code></a> to get more information about the variables.</p>
<p>The volume is used to store TLS related files. These file names are specified using <code>ZBX_TLSCAFILE</code>, <code>ZBX_TLSCRLFILE</code>, <code>ZBX_TLSKEY_FILE</code> and <code>ZBX_TLSPSKFILE</code> variables.</p>
<p>The volume is used as location of public and private keys for SSH checks and actions. It is <code>SSHKeyLocation</code> parameter in <code>zabbix_proxy.conf</code>.</p>
<p>The volume is used as location of of SSL client certificate files for client authentication. It is <code>SSLCertLocation</code> parameter in <code>zabbix_proxy.conf</code>.</p>
<p>The volume is used as location of SSL private key files for client authentication. It is <code>SSLKeyLocation</code> parameter in <code>zabbix_proxy.conf</code>.</p>
<p>The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is <code>SSLCALocation</code> parameter in <code>zabbix_proxy.conf</code>.</p>
<p>The volume is used as location of <code>snmptraps.log</code> file. It could be shared by <code>zabbix-snmptraps</code> container and inherited using <code>volumes_from</code> Podman option while creating new instance of Zabbix proxy.
SNMP traps processing feature could be enabled using shared volume and switched <code>ZBX_ENABLE_SNMP_TRAPS</code> environment variable to <code>true</code>.</p>
<p>Documentation for this image is stored in the <ahref="https://github.com/zabbix/zabbix-docker/tree/5.0/Dockerfiles/proxy-sqlite3"><code>proxy-sqlite3/</code> directory</a> of the <ahref="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <ahref="https://github.com/zabbix/zabbix-docker/blob/5.0/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
<p>If you have any problems with or questions about this image, please contact us through a <ahref="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
<h3id="known-issues">Known issues</h3>
<h2id="contributing">Contributing</h2>
<p>You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.</p>
<p>Before you start to code, we recommend discussing your plans through a <ahref="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>
