Description
<h1>What is Zabbix?</h1>
<p>Zabbix is an enterprise-class open source distributed monitoring solution.<br />
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.<br />
For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">https://zabbix.com</a>.</p>
<h1>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>
<h1>Zabbix proxy images</h1>
<p>Images are updated when new releases are published.<br />
The image uses SQLite3 database to store collected data before sending it to Zabbix server.</p>
<h1>How to use this image</h1>
<h2>Start zabbix-proxy-sqlite3</h2>
<p>Start a Zabbix proxy container as follows:</p>
<p>podman run --name some-zabbix-proxy-sqlite3 \<br />
-e ZBX_HOSTNAME=some-hostname -e ZBX_SERVER_HOST=some-zabbix-server \<br />
-d registry.connect.redhat.com/zabbix/zabbix-proxy-sqlite-62:tag</p>
<p>Where some-zabbix-proxy-sqlite3 is the name you want to assign to your container, some-hostname is the hostname, it is Hostname parameter in Zabbix proxy configuration file, some-zabbix-server is IP or DNS name of Zabbix server and tag is the tag specifying the version you want. See the list above for relevant tags.</p>
<h2>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 ZBX_PROXYMODE=1. Start Zabbix server container like this in order to link it to the Zabbix proxy container:<br />
$ podman run --name some-zabbix-server \<br />
--link some-zabbix-proxy-sqlite3:zabbix-proxy-sqlite3<br />
-d registry.connect.redhat.com/zabbix/zabbix-server-mysql-62:latest</p>
<h2>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:<br />
$ podman run --name some-zabbix-proxy-sqlite3 \<br />
--link some-zabbix-server:zabbix-server \<br />
-d registry.connect.redhat.com/zabbix/zabbix-proxy-sqlite-62:latest</p>
<h2>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 zabbix-proxy-sqlite3 container:</p>
<p>$ podman exec -ti some-zabbix-proxy-sqlite3 /bin/bash</p>
<p>The Zabbix proxy log is available through Podman's container log:</p>
<p>$ podman logs some-zabbix-proxy-sqlite3</p>
<h2>Environment Variables</h2>
<p>When you start the zabbix-proxy-sqlite3 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>ZBX_PROXYMODE</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>ZBX_HOSTNAME</p>
<p>This variable is unique, case sensitive hostname. By default, value is zabbix-proxy-sqlite3 of the container. It is Hostname parameter in <code>zabbix_proxy.conf</code>.</p>
<p>ZBX_SERVER_HOST</p>
<p>This variable is IP or DNS name of Zabbix server or Zabbix proxy. By default, value is zabbix-server. It is Server parameter in <code>zabbix_proxy.conf</code>. It is allowed to specify Zabbix server or Zabbix proxy port number using ZBX_SERVER_PORT variable. It make sense in case of non-default port for active checks.</p>
<p>ZBX_SERVER_PORT</p>
<p>This variable is port Zabbix server listening on. By default, value is 10051.</p>
<p>ZBX_LOADMODULE</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>ZBX_DEBUGLEVEL</p>
<p>The variable is used to specify debug level. By default, value is <code>3</code>. It is DebugLevel 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>
</ul>
<p>ZBX_TIMEOUT</p>
<p>The variable is used to specify timeout for processing checks. By default, value is <code>4</code>.</p>
<p>ZBX_JAVAGATEWAY_ENABLE</p>
<p>The variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is <code>false</code>.</p>
<h3>Other variables</h3>
<p>Additionally the image allows to specify many other environment variables listed below:</p>
<p>ZBX_ENABLEREMOTECOMMANDS=0 # Available since 3.4.0<br />
ZBX_LOGREMOTECOMMANDS=0 # Available since 3.4.0<br />
ZBX_SOURCEIP=<br />
ZBX_HOSTNAMEITEM=system.hostname<br />
ZBX_PROXYLOCALBUFFER=0<br />
ZBX_PROXYOFFLINEBUFFER=1<br />
ZBX_PROXYHEARTBEATFREQUENCY=60<br />
ZBX_CONFIGFREQUENCY=3600<br />
ZBX_DATASENDERFREQUENCY=1<br />
ZBX_STARTPOLLERS=5<br />
ZBX_STARTPREPROCESSORS=3 # Available since 4.2.0<br />
ZBX_IPMIPOLLERS=0<br />
ZBX_STARTPOLLERSUNREACHABLE=1<br />
ZBX_STARTTRAPPERS=5<br />
ZBX_STARTPINGERS=1<br />
ZBX_STARTDISCOVERERS=1<br />
ZBX_STARTHTTPPOLLERS=1<br />
ZBX_JAVAGATEWAY=zabbix-java-gateway<br />
ZBX_JAVAGATEWAYPORT=10052<br />
ZBX_STARTJAVAPOLLERS=0<br />
ZBX_STATSALLOWEDIP= # Available since 4.0.5<br />
ZBX_STARTVMWARECOLLECTORS=0<br />
ZBX_VMWAREFREQUENCY=60<br />
ZBX_VMWAREPERFFREQUENCY=60<br />
ZBX_VMWARECACHESIZE=8M<br />
ZBX_VMWARETIMEOUT=10<br />
ZBX_ENABLE_SNMP_TRAPS=false<br />
ZBX_LISTENIP=<br />
ZBX_HOUSEKEEPINGFREQUENCY=1<br />
ZBX_CACHESIZE=8M<br />
ZBX_STARTDBSYNCERS=4<br />
ZBX_HISTORYCACHESIZE=16M<br />
ZBX_HISTORYINDEXCACHESIZE=4M<br />
ZBX_TRAPPERIMEOUT=300<br />
ZBX_UNREACHABLEPERIOD=45<br />
ZBX_UNAVAILABLEDELAY=60<br />
ZBX_UNREACHABLEDELAY=15<br />
ZBX_LOGSLOWQUERIES=3000<br />
ZBX_TLSCONNECT=unencrypted<br />
ZBX_TLSACCEPT=unencrypted<br />
ZBX_TLSCAFILE=<br />
ZBX_TLSCRLFILE=<br />
ZBX_TLSSERVERCERTISSUER=<br />
ZBX_TLSSERVERCERTSUBJECT=<br />
ZBX_TLSCERTFILE=<br />
ZBX_TLSKEYFILE=<br />
ZBX_TLSPSKIDENTITY=<br />
ZBX_TLSPSKFILE=<br />
ZBX_TLSCIPHERALL= # Available since 4.4.7<br />
ZBX_TLSCIPHERALL13= # Available since 4.4.7<br />
ZBX_TLSCIPHERCERT= # Available since 4.4.7<br />
ZBX_TLSCIPHERCERT13= # Available since 4.4.7<br />
ZBX_TLSCIPHERPSK= # Available since 4.4.7<br />
ZBX_TLSCIPHERPSK13= # Available since 4.4.7</p>
<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, ZBX_LOGSLOWQUERIES= LogSlowQueries.</p>
<p>Please use official documentation for <a href="https://www.zabbix.com/documentation/current/manual/appendix/config/zabb..."><code>zabbix_proxy.conf</code></a> to get more information about the variables.</p>
<h2>Allowed volumes for the Zabbix proxy container</h2>
<p><code>/usr/lib/zabbix/externalscripts</code></p>
<p>The volume is used by External checks (type of items). It is ExternalScripts parameter in <code>zabbix_proxy.conf</code>.</p>
<p><code>/var/lib/zabbix/modules</code></p>
<p>The volume allows load additional modules and extend Zabbix proxy using LoadModule feature.</p>
<p><code>/var/lib/zabbix/enc</code></p>
<p>The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCRLFILE, ZBX_TLSKEY_FILE and ZBX_TLSPSKFILE variables.</p>
<p><code>/var/lib/zabbix/ssh_keys</code></p>
<p>The volume is used as location of public and private keys for SSH checks and actions. It is SSHKeyLocation parameter in <code>zabbix_proxy.conf</code>.</p>
<p><code>/var/lib/zabbix/ssl/certs</code></p>
<p>The volume is used as location of of SSL client certificate files for client authentication. It is SSLCertLocation parameter in <code>zabbix_proxy.conf</code>.</p>
<p><code>/var/lib/zabbix/ssl/keys</code></p>
<p>The volume is used as location of SSL private key files for client authentication. It is SSLKeyLocation parameter in <code>zabbix_proxy.conf</code>.</p>
<p><code>/var/lib/zabbix/ssl/ssl_ca</code></p>
<p>The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is SSLCALocation parameter in <code>zabbix_proxy.conf</code>.</p>
<p><code>/var/lib/zabbix/snmptraps</code></p>
<p>The volume is used as location of snmptraps.log file. It could be shared by zabbix-snmptraps 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 ZBX_ENABLE_SNMP_TRAPS environment variable to <code>true</code>.</p>
<p><code>/var/lib/zabbix/mibs</code></p>
<p>The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to <code>/var/lib/zabbix/mibs</code>.</p>
<h1>User Feedback</h1>
<h2>Documentation</h2>
<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/5.4/Dockerfiles/proxy-sqlite3/rhel/"><code>proxy-sqlite3/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/master/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
<h2>Issues</h2>
<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
<h3>Known issues</h3>
