mirror of
https://github.com/zabbix/zabbix-docker.git
synced 2024-11-26 01:34:01 +01:00
Merge pull request #1304 from zabbix/trunk_tzdata
Updated RedHat documentation
This commit is contained in:
Alexey Pustovalov
GitHub
commit
29f71b2433
195
Dockerfiles/server-pgsql/rhel/README.html
Normal file
195
Dockerfiles/server-pgsql/rhel/README.html
Normal file
@ -0,0 +1,195 @@
|
|||||||
|
<p><img src="https://assets.zabbix.com/img/logo/zabbix_logo_500x131.png" alt="logo"></p>
|
||||||
|
<h1 id="what-is-zabbix-">What is Zabbix?</h1>
|
||||||
|
<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 <a href="https://hub.docker.com/u/zabbix/">https://hub.docker.com/u/zabbix/</a> and <a href="https://zabbix.com">https://zabbix.com</a></p>
|
||||||
|
<h1 id="what-is-zabbix-server-">What is Zabbix server?</h1>
|
||||||
|
<p>Zabbix server is the central process of Zabbix software.</p>
|
||||||
|
<p>The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.</p>
|
||||||
|
<h1 id="zabbix-server-images">Zabbix server images</h1>
|
||||||
|
<p>Images are updated when new releases are published.</p>
|
||||||
|
<p>The image uses PostgreSQL database. It uses the next procedure to start:</p>
|
||||||
|
<ul>
|
||||||
|
<li>Checking database availability</li>
|
||||||
|
<li>Checking of having <code>POSTGRES_DB</code> database. Creating <code>POSTGRES_DB</code> database name if it does not exist</li>
|
||||||
|
<li>Checking of having <code>dbversion</code> table. Creating Zabbix server database schema and upload initial data sample if no <code>dbversion</code> table</li>
|
||||||
|
</ul>
|
||||||
|
<h1 id="how-to-use-this-image">How to use this image</h1>
|
||||||
|
<h2 id="start-zabbix-server-pgsql-">Start <code>zabbix-server-pgsql</code></h2>
|
||||||
|
<p>Start a Zabbix server container as follows:</p>
|
||||||
|
<pre><code>podman <span class="hljs-keyword">run</span><span class="bash"> --name some-zabbix-server-pgsql <span class="hljs-_">-e</span> DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> <span class="hljs-_">-e</span> POSTGRES_USER=<span class="hljs-string">"some-user"</span> <span class="hljs-_">-e</span> POSTGRES_PASSWORD=<span class="hljs-string">"some-password"</span> <span class="hljs-_">-d</span> zabbix/zabbix-server-pgsql:tag</span>
|
||||||
|
</code></pre><p>Where <code>some-zabbix-server-pgsql</code> is the name you want to assign to your container, <code>some-postgres-server</code> is IP or DNS name of PostgreSQL server, <code>some-user</code> is user to connect to Zabbix database on PostgreSQL server, <code>some-password</code> is the password to connect to PostgreSQL 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>podman 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>
|
||||||
|
<h2 id="container-shell-access-and-viewing-zabbix-server-logs">Container shell access and viewing Zabbix server 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-server-pgsql</code> container:</p>
|
||||||
|
<pre><code class="lang-console">$ podman exec -ti <span class="hljs-keyword">some</span>-zabbix-server-pgsql /bin/bash
|
||||||
|
</code></pre>
|
||||||
|
<p>The Zabbix server log is available through Podman's container log:</p>
|
||||||
|
<pre><code class="lang-console">$ podman logs <span class="hljs-keyword">some</span>-zabbix-server-pgsql
|
||||||
|
</code></pre>
|
||||||
|
<h2 id="environment-variables">Environment Variables</h2>
|
||||||
|
<p>When you start the <code>zabbix-server-pgsql</code> image, you can adjust the configuration of the Zabbix server by passing one or more environment variables on the <code>podman run</code> command line.</p>
|
||||||
|
<h3 id="-db_server_host-"><code>DB_SERVER_HOST</code></h3>
|
||||||
|
<p>This variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'</p>
|
||||||
|
<h3 id="-db_server_port-"><code>DB_SERVER_PORT</code></h3>
|
||||||
|
<p>This variable is port of PostgreSQL server. By default, value is '5432'.</p>
|
||||||
|
<h3 id="-postgres_user-postgres_password-postgres_user_file-postgres_password_file-"><code>POSTGRES_USER</code>, <code>POSTGRES_PASSWORD</code>, <code>POSTGRES_USER_FILE</code>, <code>POSTGRES_PASSWORD_FILE</code></h3>
|
||||||
|
<p>These variables are used by Zabbix server to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either <code>POSTGRES_USER</code> or <code>POSTGRES_USER_FILE</code>!</p>
|
||||||
|
<pre><code class="lang-console">podman run --name some-zabbix-server-pgsql -e DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> -v .<span class="hljs-regexp">/.POSTGRES_USER:/</span>run<span class="hljs-regexp">/secrets/</span>POSTGRES_USER -e POSTGRES_USER_FILE=<span class="hljs-regexp">/run/</span>secrets<span class="hljs-regexp">/POSTGRES_USER -v ./</span>.<span class="hljs-string">POSTGRES_PASSWORD:</span><span class="hljs-regexp">/run/</span>secrets<span class="hljs-regexp">/POSTGRES_PASSWORD -e POSTGRES_PASSWORD_FILE=/</span>var<span class="hljs-regexp">/run/</span>secrets<span class="hljs-regexp">/POSTGRES_PASSWORD -d zabbix/</span>zabbix-server-<span class="hljs-string">pgsql:</span>tag
|
||||||
|
</code></pre>
|
||||||
|
<p>With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!</p>
|
||||||
|
<pre><code class="lang-console"><span class="hljs-built_in">printf</span> <span class="hljs-string">"zabbix"</span> | podman secret create POSTGRES_USER -
|
||||||
|
<span class="hljs-built_in">printf</span> <span class="hljs-string">"zabbix"</span> | podman secret create POSTGRES_PASSWORD -
|
||||||
|
podman run --name some-zabbix-server-pgsql <span class="hljs-_">-e</span> DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> <span class="hljs-_">-e</span> POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER <span class="hljs-_">-e</span> POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD <span class="hljs-_">-d</span> zabbix/zabbix-server-pgsql:tag
|
||||||
|
</code></pre>
|
||||||
|
<p>By default, values for <code>POSTGRES_USER</code> and <code>POSTGRES_PASSWORD</code> are <code>zabbix</code>, <code>zabbix</code>.</p>
|
||||||
|
<h3 id="-postgres_db-"><code>POSTGRES_DB</code></h3>
|
||||||
|
<p>The variable is Zabbix database name. By default, value is <code>zabbix</code>.</p>
|
||||||
|
<h3 id="-postgres_use_implicit_search_path-"><code>POSTGRES_USE_IMPLICIT_SEARCH_PATH</code></h3>
|
||||||
|
<p>In some setups, for example including <a href="https://www.pgbouncer.org">PgBouncer</a>, setting the <code>search_path</code> via connection parameters fails. If this variable is set to <code>"true"</code>, the image skips setting the <code>search_path</code> and trusts that the <code>search_path</code> of the Zabbix user is setup correctly in PostgreSQL database.</p>
|
||||||
|
<h3 id="-zbx_loadmodule-"><code>ZBX_LOADMODULE</code></h3>
|
||||||
|
<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>
|
||||||
|
<h3 id="-zbx_debuglevel-"><code>ZBX_DEBUGLEVEL</code></h3>
|
||||||
|
<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>
|
||||||
|
</ul>
|
||||||
|
<h3 id="-zbx_timeout-"><code>ZBX_TIMEOUT</code></h3>
|
||||||
|
<p>The variable is used to specify timeout for processing checks. By default, value is <code>4</code>.</p>
|
||||||
|
<h3 id="-zbx_javagateway_enable-"><code>ZBX_JAVAGATEWAY_ENABLE</code></h3>
|
||||||
|
<p>The variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is <code>false</code>.</p>
|
||||||
|
<h3 id="other-variables">Other variables</h3>
|
||||||
|
<p>Additionally the image allows to specify many other environment variables listed below:</p>
|
||||||
|
<pre><code><span class="hljs-attr">ZBX_ALLOWUNSUPPORTEDDBVERSIONS</span>=<span class="hljs-number">0</span> # Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_DBTLSCONNECT</span>= # Available since <span class="hljs-number">5.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_DBTLSCAFILE</span>= # Available since <span class="hljs-number">5.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_DBTLSCERTFILE</span>= # Available since <span class="hljs-number">5.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_DBTLSKEYFILE</span>= # Available since <span class="hljs-number">5.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_DBTLSCIPHER</span>= # Available since <span class="hljs-number">5.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_DBTLSCIPHER13</span>= # Available since <span class="hljs-number">5.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_VAULTDBPATH</span>= # Available since <span class="hljs-number">5.2</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_VAULTURL</span>=https://<span class="hljs-number">127.0</span>.<span class="hljs-number">0.1</span>:<span class="hljs-number">8200</span> # Available since <span class="hljs-number">5.2</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">VAULT_TOKEN</span>= # Available since <span class="hljs-number">5.2</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_LISTENIP</span>=
|
||||||
|
<span class="hljs-attr">ZBX_LISTENPORT</span>=<span class="hljs-number">10051</span>
|
||||||
|
<span class="hljs-attr">ZBX_LISTENBACKLOG</span>=
|
||||||
|
<span class="hljs-attr">ZBX_STARTREPORTWRITERS</span>=<span class="hljs-number">0</span> # Available since <span class="hljs-number">5.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_WEBSERVICEURL</span>=http://zabbix-web-service:<span class="hljs-number">10053</span>/report # Available since <span class="hljs-number">5.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_SERVICEMANAGERSYNCFREQUENCY</span>=<span class="hljs-number">60</span> # Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_HISTORYSTORAGEURL</span>= # Available since <span class="hljs-number">3.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_HISTORYSTORAGETYPES</span>=uint,dbl,str,log,text # Available since <span class="hljs-number">3.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTPOLLERS</span>=<span class="hljs-number">5</span>
|
||||||
|
<span class="hljs-attr">ZBX_IPMIPOLLERS</span>=<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTCONNECTORS</span>=<span class="hljs-number">0</span> # Available since <span class="hljs-number">6.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTPREPROCESSORS</span>=<span class="hljs-number">3</span> # Available since <span class="hljs-number">3.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTPOLLERSUNREACHABLE</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTTRAPPERS</span>=<span class="hljs-number">5</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTPINGERS</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTDISCOVERERS</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTHISTORYPOLLERS</span>=<span class="hljs-number">5</span> # Available since <span class="hljs-number">5.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTHTTPPOLLERS</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTODBCPOLLERS</span>=<span class="hljs-number">1</span> # Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTTIMERS</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTESCALATORS</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTALERTERS</span>=<span class="hljs-number">3</span> # Available since <span class="hljs-number">3.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_JAVAGATEWAY</span>=zabbix-java-gateway
|
||||||
|
<span class="hljs-attr">ZBX_JAVAGATEWAYPORT</span>=<span class="hljs-number">10052</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTJAVAPOLLERS</span>=<span class="hljs-number">5</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTLLDPROCESSORS</span>=<span class="hljs-number">2</span> # Available since <span class="hljs-number">4.2</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_STATSALLOWEDIP</span>= # Available since <span class="hljs-number">4.0</span>.<span class="hljs-number">5</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTVMWARECOLLECTORS</span>=<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_VMWAREFREQUENCY</span>=<span class="hljs-number">60</span>
|
||||||
|
<span class="hljs-attr">ZBX_VMWAREPERFFREQUENCY</span>=<span class="hljs-number">60</span>
|
||||||
|
<span class="hljs-attr">ZBX_VMWARECACHESIZE</span>=<span class="hljs-number">8</span>M
|
||||||
|
<span class="hljs-attr">ZBX_VMWARETIMEOUT</span>=<span class="hljs-number">10</span>
|
||||||
|
<span class="hljs-attr">ZBX_ENABLE_SNMP_TRAPS</span>=<span class="hljs-literal">false</span>
|
||||||
|
<span class="hljs-attr">ZBX_SOURCEIP</span>=
|
||||||
|
<span class="hljs-attr">ZBX_HOUSEKEEPINGFREQUENCY</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_MAXHOUSEKEEPERDELETE</span>=<span class="hljs-number">5000</span>
|
||||||
|
<span class="hljs-attr">ZBX_PROBLEMHOUSEKEEPINGFREQUENCY</span>=<span class="hljs-number">60</span> # Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_SENDERFREQUENCY</span>=<span class="hljs-number">30</span> # Depcrecated since <span class="hljs-number">3.4</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_CACHESIZE</span>=<span class="hljs-number">8</span>M
|
||||||
|
<span class="hljs-attr">ZBX_CACHEUPDATEFREQUENCY</span>=<span class="hljs-number">10</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTDBSYNCERS</span>=<span class="hljs-number">4</span>
|
||||||
|
<span class="hljs-attr">ZBX_EXPORTFILESIZE</span>=<span class="hljs-number">1</span>G # Available since <span class="hljs-number">4.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_EXPORTTYPE</span>= # Available since <span class="hljs-number">5.0</span>.<span class="hljs-number">10</span> and <span class="hljs-number">5.2</span>.<span class="hljs-number">6</span>
|
||||||
|
<span class="hljs-attr">ZBX_AUTOHANODENAME</span>=fqdn # Allowed values: fqdn, hostname. Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_HANODENAME</span>= # Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_AUTONODEADDRESS</span>=fqdn # Allowed values: fqdn, hostname. Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_NODEADDRESSPORT</span>=<span class="hljs-number">10051</span> # Allowed to use with ZBX_AUTONODEADDRESS variable <span class="hljs-literal">on</span>ly. Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_NODEADDRESS</span>=localhost # Available since <span class="hljs-number">6.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_HISTORYCACHESIZE</span>=<span class="hljs-number">16</span>M
|
||||||
|
<span class="hljs-attr">ZBX_HISTORYINDEXCACHESIZE</span>=<span class="hljs-number">4</span>M
|
||||||
|
<span class="hljs-attr">ZBX_HISTORYSTORAGEDATEINDEX</span>=<span class="hljs-number">0</span> # Available since <span class="hljs-number">4.0</span>.<span class="hljs-number">0</span>
|
||||||
|
<span class="hljs-attr">ZBX_TRENDCACHESIZE</span>=<span class="hljs-number">4</span>M
|
||||||
|
<span class="hljs-attr">ZBX_TRENDFUNCTIONCACHESIZE</span>=<span class="hljs-number">4</span>M
|
||||||
|
<span class="hljs-attr">ZBX_VALUECACHESIZE</span>=<span class="hljs-number">8</span>M
|
||||||
|
<span class="hljs-attr">ZBX_TRAPPERTIMEOUT</span>=<span class="hljs-number">300</span>
|
||||||
|
<span class="hljs-attr">ZBX_UNREACHABLEPERIOD</span>=<span class="hljs-number">45</span>
|
||||||
|
<span class="hljs-attr">ZBX_UNAVAILABLEDELAY</span>=<span class="hljs-number">60</span>
|
||||||
|
<span class="hljs-attr">ZBX_UNREACHABLEDELAY</span>=<span class="hljs-number">15</span>
|
||||||
|
<span class="hljs-attr">ZBX_LOGSLOWQUERIES</span>=<span class="hljs-number">3000</span>
|
||||||
|
<span class="hljs-attr">ZBX_STARTPROXYPOLLERS</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_PROXYCONFIGFREQUENCY</span>=<span class="hljs-number">10</span>
|
||||||
|
<span class="hljs-attr">ZBX_PROXYDATAFREQUENCY</span>=<span class="hljs-number">1</span>
|
||||||
|
<span class="hljs-attr">ZBX_TLSCAFILE</span>=
|
||||||
|
<span class="hljs-attr">ZBX_TLSCRLFILE</span>=
|
||||||
|
<span class="hljs-attr">ZBX_TLSCERTFILE</span>=
|
||||||
|
<span class="hljs-attr">ZBX_TLSKEYFILE</span>=
|
||||||
|
<span class="hljs-attr">ZBX_TLSCIPHERALL</span>= # Available since <span class="hljs-number">4.4</span>.<span class="hljs-number">7</span>
|
||||||
|
<span class="hljs-attr">ZBX_TLSCIPHERALL13</span>= # Available since <span class="hljs-number">4.4</span>.<span class="hljs-number">7</span>
|
||||||
|
<span class="hljs-attr">ZBX_TLSCIPHERCERT</span>= # Available since <span class="hljs-number">4.4</span>.<span class="hljs-number">7</span>
|
||||||
|
<span class="hljs-attr">ZBX_TLSCIPHERCERT13</span>= # Available since <span class="hljs-number">4.4</span>.<span class="hljs-number">7</span>
|
||||||
|
<span class="hljs-attr">ZBX_TLSCIPHERPSK</span>= # Available since <span class="hljs-number">4.4</span>.<span class="hljs-number">7</span>
|
||||||
|
<span class="hljs-attr">ZBX_TLSCIPHERPSK13</span>= # Available since <span class="hljs-number">4.4</span>.<span class="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_server.conf</code>. For example, <code>ZBX_LOGSLOWQUERIES</code> = <code>LogSlowQueries</code>.</p>
|
||||||
|
<p>Please use official documentation for <a href="https://www.zabbix.com/documentation/current/manual/appendix/config/zabbix_server"><code>zabbix_server.conf</code></a> to get more information about the variables.</p>
|
||||||
|
<h2 id="allowed-volumes-for-the-zabbix-server-container">Allowed volumes for the Zabbix server container</h2>
|
||||||
|
<h3 id="-usr-lib-zabbix-alertscripts-"><code>/usr/lib/zabbix/alertscripts</code></h3>
|
||||||
|
<p>The volume is used for custom alert scripts. It is <code>AlertScriptsPath</code> parameter in <code>zabbix_server.conf</code>.</p>
|
||||||
|
<h3 id="-usr-lib-zabbix-externalscripts-"><code>/usr/lib/zabbix/externalscripts</code></h3>
|
||||||
|
<p>The volume is used by External checks (type of items). It is <code>ExternalScripts</code> parameter in <code>zabbix_server.conf</code>.</p>
|
||||||
|
<h3 id="-var-lib-zabbix-modules-"><code>/var/lib/zabbix/modules</code></h3>
|
||||||
|
<p>The volume allows load additional modules and extend Zabbix server using <code>LoadModule</code> feature.</p>
|
||||||
|
<h3 id="-var-lib-zabbix-enc-"><code>/var/lib/zabbix/enc</code></h3>
|
||||||
|
<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>
|
||||||
|
<h3 id="-var-lib-zabbix-ssh_keys-"><code>/var/lib/zabbix/ssh_keys</code></h3>
|
||||||
|
<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_server.conf</code>.</p>
|
||||||
|
<h3 id="-var-lib-zabbix-ssl-certs-"><code>/var/lib/zabbix/ssl/certs</code></h3>
|
||||||
|
<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_server.conf</code>.</p>
|
||||||
|
<h3 id="-var-lib-zabbix-ssl-keys-"><code>/var/lib/zabbix/ssl/keys</code></h3>
|
||||||
|
<p>The volume is used as location of SSL private key files for client authentication. It is <code>SSLKeyLocation</code> parameter in <code>zabbix_server.conf</code>.</p>
|
||||||
|
<h3 id="-var-lib-zabbix-ssl-ssl_ca-"><code>/var/lib/zabbix/ssl/ssl_ca</code></h3>
|
||||||
|
<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_server.conf</code>.</p>
|
||||||
|
<h3 id="-var-lib-zabbix-snmptraps-"><code>/var/lib/zabbix/snmptraps</code></h3>
|
||||||
|
<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 server.
|
||||||
|
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>
|
||||||
|
<h3 id="-var-lib-zabbix-mibs-"><code>/var/lib/zabbix/mibs</code></h3>
|
||||||
|
<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>
|
||||||
|
<h3 id="-var-lib-zabbix-export-"><code>/var/lib/zabbix/export</code></h3>
|
||||||
|
<p>Directory for real-time export of events, history and trends in newline-delimited JSON format. Could be enabled using <code>ZBX_EXPORTFILESIZE</code> environment variable.</p>
|
||||||
|
<h1 id="user-feedback">User Feedback</h1>
|
||||||
|
<h2 id="documentation">Documentation</h2>
|
||||||
|
<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/trunk/Dockerfiles/server-pgsql"><code>server-pgsql/</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/trunk/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
|
||||||
|
<h2 id="issues">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 id="known-issues">Known issues</h3>
|
||||||
|
<h2 id="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 <a href="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>
|
||||||
143
Dockerfiles/web-nginx-pgsql/rhel/README.html
Normal file
143
Dockerfiles/web-nginx-pgsql/rhel/README.html
Normal file
@ -0,0 +1,143 @@
|
|||||||
|
<p><img src="https://assets.zabbix.com/img/logo/zabbix_logo_500x131.png" alt="logo"></p>
|
||||||
|
<h1 id="what-is-zabbix-">What is Zabbix?</h1>
|
||||||
|
<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 <a href="https://hub.docker.com/u/zabbix/">https://hub.docker.com/u/zabbix/</a> and <a href="https://zabbix.com">https://zabbix.com</a></p>
|
||||||
|
<h1 id="what-is-zabbix-web-interface-">What is Zabbix web interface?</h1>
|
||||||
|
<p>Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.</p>
|
||||||
|
<h1 id="zabbix-web-interface-images">Zabbix web interface images</h1>
|
||||||
|
<p>These are the only official Zabbix web interface Podman images. Images are updated when new releases are published.</p>
|
||||||
|
<p>Zabbix web interface available in four editions:</p>
|
||||||
|
<ul>
|
||||||
|
<li>Zabbix web-interface based on Apache2 web server with MySQL database support</li>
|
||||||
|
<li>Zabbix web-interface based on Apache2 web server with PostgreSQL database support</li>
|
||||||
|
<li>Zabbix web-interface based on Nginx web server with MySQL database support</li>
|
||||||
|
<li>Zabbix web-interface based on Nginx web server with PostgreSQL database support</li>
|
||||||
|
</ul>
|
||||||
|
<p>The image based on Nginx web server with PostgreSQL database support.</p>
|
||||||
|
<h1 id="how-to-use-this-image">How to use this image</h1>
|
||||||
|
<h2 id="start-zabbix-web-nginx-pgsql-">Start <code>zabbix-web-nginx-pgsql</code></h2>
|
||||||
|
<p>Start a Zabbix web-interface container as follows:</p>
|
||||||
|
<pre><code>podman <span class="hljs-keyword">run</span><span class="bash"> --name some-zabbix-web-nginx-pgsql <span class="hljs-_">-e</span> DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> <span class="hljs-_">-e</span> POSTGRES_USER=<span class="hljs-string">"some-user"</span> <span class="hljs-_">-e</span> POSTGRES_PASSWORD=<span class="hljs-string">"some-password"</span> <span class="hljs-_">-e</span> ZBX_SERVER_HOST=<span class="hljs-string">"some-zabbix-server"</span> <span class="hljs-_">-e</span> PHP_TZ=<span class="hljs-string">"some-timezone"</span> <span class="hljs-_">-d</span> zabbix/zabbix-web-nginx-pgsql:tag</span>
|
||||||
|
</code></pre><p>Where <code>some-zabbix-web-nginx-pgsql</code> is the name you want to assign to your container, <code>some-postgres-server</code> is IP or DNS name of PostgreSQL server, <code>some-user</code> is user to connect to Zabbix database on PostgreSQL server, <code>some-password</code> is the password to connect to PostgreSQL server, <code>some-zabbix-server</code> is IP or DNS name of Zabbix server or proxy, <code>some-timezone</code> is PHP like timezone name and <code>tag</code> is the tag specifying the version you want.</p>
|
||||||
|
<h2 id="linking-the-container-to-zabbix-server">Linking the container to Zabbix server</h2>
|
||||||
|
<pre><code>podman <span class="hljs-keyword">run</span><span class="bash"> --name some-zabbix-web-nginx-pgsql --link some-zabbix-server:zabbix-server <span class="hljs-_">-e</span> DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> <span class="hljs-_">-e</span> POSTGRES_USER=<span class="hljs-string">"some-user"</span> <span class="hljs-_">-e</span> POSTGRES_PASSWORD=<span class="hljs-string">"some-password"</span> <span class="hljs-_">-e</span> ZBX_SERVER_HOST=<span class="hljs-string">"some-zabbix-server"</span> <span class="hljs-_">-e</span> PHP_TZ=<span class="hljs-string">"some-timezone"</span> <span class="hljs-_">-d</span> zabbix/zabbix-web-nginx-pgsql:tag</span>
|
||||||
|
</code></pre><h2 id="linking-the-container-to-postgresql-database">Linking the container to PostgreSQL database</h2>
|
||||||
|
<pre><code>podman <span class="hljs-keyword">run</span><span class="bash"> --name some-zabbix-web-nginx-pgsql --link some-postgres-server:postgres <span class="hljs-_">-e</span> DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> <span class="hljs-_">-e</span> POSTGRES_USER=<span class="hljs-string">"some-user"</span> <span class="hljs-_">-e</span> POSTGRES_PASSWORD=<span class="hljs-string">"some-password"</span> <span class="hljs-_">-e</span> ZBX_SERVER_HOST=<span class="hljs-string">"some-zabbix-server"</span> <span class="hljs-_">-e</span> PHP_TZ=<span class="hljs-string">"some-timezone"</span> <span class="hljs-_">-d</span> zabbix/zabbix-web-nginx-pgsql:tag</span>
|
||||||
|
</code></pre><h2 id="container-shell-access-and-viewing-zabbix-web-interface-logs">Container shell access and viewing Zabbix web interface 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-web-nginx-pgsql</code> container:</p>
|
||||||
|
<pre><code class="lang-console">$ podman exec -ti <span class="hljs-keyword">some</span>-zabbix-web-nginx-pgsql /bin/bash
|
||||||
|
</code></pre>
|
||||||
|
<p>The Zabbix web interface log is available through Podman's container log:</p>
|
||||||
|
<pre><code class="lang-console">$ podman logs <span class="hljs-keyword">some</span>-zabbix-web-nginx-pgsql
|
||||||
|
</code></pre>
|
||||||
|
<h2 id="environment-variables">Environment Variables</h2>
|
||||||
|
<p>When you start the <code>zabbix-web-nginx-pgsql</code> image, you can adjust the configuration of the Zabbix web interface by passing one or more environment variables on the <code>podman run</code> command line.</p>
|
||||||
|
<h3 id="-zbx_server_host-"><code>ZBX_SERVER_HOST</code></h3>
|
||||||
|
<p>This variable is IP or DNS name of Zabbix server. By default, value is <code>zabbix-server</code>.</p>
|
||||||
|
<h3 id="-zbx_server_port-"><code>ZBX_SERVER_PORT</code></h3>
|
||||||
|
<p>This variable is port Zabbix server listening on. By default, value is <code>10051</code>.</p>
|
||||||
|
<h3 id="-db_server_host-"><code>DB_SERVER_HOST</code></h3>
|
||||||
|
<p>This variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'</p>
|
||||||
|
<h3 id="-db_server_port-"><code>DB_SERVER_PORT</code></h3>
|
||||||
|
<p>This variable is port of PostgreSQL server. By default, value is '5432'.</p>
|
||||||
|
<h3 id="-postgres_user-postgres_password-postgres_user_file-postgres_password_file-"><code>POSTGRES_USER</code>, <code>POSTGRES_PASSWORD</code>, <code>POSTGRES_USER_FILE</code>, <code>POSTGRES_PASSWORD_FILE</code></h3>
|
||||||
|
<p>These variables are used by Zabbix web interface to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either <code>POSTGRES_USER</code> or <code>POSTGRES_USER_FILE</code>!</p>
|
||||||
|
<pre><code class="lang-console">podman <span class="hljs-keyword">run</span><span class="bash"> --name some-zabbix-web-nginx-pgsql <span class="hljs-_">-e</span> DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> -v ./.POSTGRES_USER:/run/secrets/POSTGRES_USER <span class="hljs-_">-e</span> POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -v ./.POSTGRES_PASSWORD:/run/secrets/POSTGRES_PASSWORD <span class="hljs-_">-e</span> POSTGRES_PASSWORD_FILE=/var/run/secrets/POSTGRES_PASSWORD <span class="hljs-_">-e</span> ZBX_SERVER_HOST=<span class="hljs-string">"some-zabbix-server"</span> <span class="hljs-_">-e</span> PHP_TZ=<span class="hljs-string">"some-timezone"</span> <span class="hljs-_">-d</span> zabbix/zabbix-web-nginx-pgsql:tag</span>
|
||||||
|
</code></pre>
|
||||||
|
<p>With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!</p>
|
||||||
|
<pre><code class="lang-console"><span class="hljs-built_in">printf</span> <span class="hljs-string">"zabbix"</span> | podman secret create POSTGRES_USER -
|
||||||
|
<span class="hljs-built_in">printf</span> <span class="hljs-string">"zabbix"</span> | podman secret create POSTGRES_PASSWORD -
|
||||||
|
podman run --name some-zabbix-web-nginx-pgsql <span class="hljs-_">-e</span> DB_SERVER_HOST=<span class="hljs-string">"some-postgres-server"</span> <span class="hljs-_">-e</span> POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER <span class="hljs-_">-e</span> POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD <span class="hljs-_">-e</span> ZBX_SERVER_HOST=<span class="hljs-string">"some-zabbix-server"</span> <span class="hljs-_">-e</span> PHP_TZ=<span class="hljs-string">"some-timezone"</span> <span class="hljs-_">-d</span> zabbix/zabbix-web-nginx-pgsql:tag
|
||||||
|
</code></pre>
|
||||||
|
<p>By default, values for <code>POSTGRES_USER</code> and <code>POSTGRES_PASSWORD</code> are <code>zabbix</code>, <code>zabbix</code>.</p>
|
||||||
|
<h3 id="-postgres_db-"><code>POSTGRES_DB</code></h3>
|
||||||
|
<p>The variable is Zabbix database name. By default, value is <code>zabbix</code>.</p>
|
||||||
|
<h3 id="-postgres_use_implicit_search_path-"><code>POSTGRES_USE_IMPLICIT_SEARCH_PATH</code></h3>
|
||||||
|
<p>In some setups, for example including <a href="https://www.pgbouncer.org">PgBouncer</a>, setting the <code>search_path</code> via connection parameters fails. If this variable is set to <code>"true"</code>, the image skips setting the <code>search_path</code> and trusts that the <code>search_path</code> of the Zabbix user is setup correctly in PostgreSQL database.</p>
|
||||||
|
<h3 id="-zbx_historystorageurl-"><code>ZBX_HISTORYSTORAGEURL</code></h3>
|
||||||
|
<p>History storage HTTP[S] URL. This parameter is used for Elasticsearch setup. Available since 3.4.5.</p>
|
||||||
|
<h3 id="-zbx_historystoragetypes-"><code>ZBX_HISTORYSTORAGETYPES</code></h3>
|
||||||
|
<p>Array of value types to be sent to the history storage. An example: ['uint', 'dbl']. This parameter is used for Elasticsearch setup. Available since 3.4.5.</p>
|
||||||
|
<h3 id="-php_tz-"><code>PHP_TZ</code></h3>
|
||||||
|
<p>The variable is timezone in PHP format. Full list of supported timezones are available on <a href="http://php.net/manual/en/timezones.php"><code>php.net</code></a>. By default, value is 'Europe/Riga' and system timezone since Zabbix 5.2.0.</p>
|
||||||
|
<h3 id="-zbx_server_name-"><code>ZBX_SERVER_NAME</code></h3>
|
||||||
|
<p>The variable is visible Zabbix installation name in right or left top corner of the web interface.</p>
|
||||||
|
<h3 id="-db_double_ieee754-"><code>DB_DOUBLE_IEEE754</code></h3>
|
||||||
|
<p>Use IEEE754 compatible value range for 64-bit Numeric (float) history values. Available since 5.0.0. Enabled by default.</p>
|
||||||
|
<h3 id="-enable_web_access_log-"><code>ENABLE_WEB_ACCESS_LOG</code></h3>
|
||||||
|
<p>The variable sets the Access Log directive for Web server. By default, value corresponds to standard output.</p>
|
||||||
|
<h3 id="-http_index_file-"><code>HTTP_INDEX_FILE</code></h3>
|
||||||
|
<p>The variable controls default index page. By default, <code>index.php</code>.</p>
|
||||||
|
<h3 id="-expose_web_server_info-"><code>EXPOSE_WEB_SERVER_INFO</code></h3>
|
||||||
|
<p>The variable allows to hide Web server and PHP versions. By default, <code>on</code>.</p>
|
||||||
|
<h3 id="-zbx_maxexecutiontime-"><code>ZBX_MAXEXECUTIONTIME</code></h3>
|
||||||
|
<p>The varable is PHP <code>max_execution_time</code> option. By default, value is <code>300</code>.</p>
|
||||||
|
<h3 id="-zbx_memorylimit-"><code>ZBX_MEMORYLIMIT</code></h3>
|
||||||
|
<p>The varable is PHP <code>memory_limit</code> option. By default, value is <code>128M</code>.</p>
|
||||||
|
<h3 id="-zbx_postmaxsize-"><code>ZBX_POSTMAXSIZE</code></h3>
|
||||||
|
<p>The varable is PHP <code>post_max_size</code> option. By default, value is <code>16M</code>.</p>
|
||||||
|
<h3 id="-zbx_uploadmaxfilesize-"><code>ZBX_UPLOADMAXFILESIZE</code></h3>
|
||||||
|
<p>The varable is PHP <code>upload_max_filesize</code> option. By default, value is <code>2M</code>.</p>
|
||||||
|
<h3 id="-zbx_maxinputtime-"><code>ZBX_MAXINPUTTIME</code></h3>
|
||||||
|
<p>The varable is PHP <code>max_input_time</code> option. By default, value is <code>300</code>.</p>
|
||||||
|
<h3 id="-zbx_session_name-"><code>ZBX_SESSION_NAME</code></h3>
|
||||||
|
<p>The variable is Zabbix frontend <a href="https://www.zabbix.com/documentation/current/manual/web_interface/definitions">definition</a>. String used as the name of the Zabbix frontend session cookie. By default, value is <code>zbx_sessionid</code>.</p>
|
||||||
|
<h3 id="-zbx_deny_gui_access-"><code>ZBX_DENY_GUI_ACCESS</code></h3>
|
||||||
|
<p>Enable (<code>true</code>) maintenance mode for Zabbix web-interface.</p>
|
||||||
|
<h3 id="-zbx_gui_access_ip_range-"><code>ZBX_GUI_ACCESS_IP_RANGE</code></h3>
|
||||||
|
<p>Array of IP addresses which are allowed for accessing to Zabbix web-interface during maintenance period.</p>
|
||||||
|
<h3 id="-zbx_gui_warning_msg-"><code>ZBX_GUI_WARNING_MSG</code></h3>
|
||||||
|
<p>Information message about maintenance period for Zabbix web-interface.</p>
|
||||||
|
<h3 id="-zbx_db_encryption-"><code>ZBX_DB_ENCRYPTION</code></h3>
|
||||||
|
<p>The variable allows to activate encryption for connections to Zabbix database. Even if no other environment variables are specified, connections will be TLS-encrypted if <code>ZBX_DB_ENCRYPTION=true</code> specified. Available since 5.0.0. Disabled by default.</p>
|
||||||
|
<h3 id="-zbx_db_key_file-"><code>ZBX_DB_KEY_FILE</code></h3>
|
||||||
|
<p>The variable allows to specify the full path to a valid TLS key file. Available since 5.0.0.</p>
|
||||||
|
<h3 id="-zbx_db_cert_file-"><code>ZBX_DB_CERT_FILE</code></h3>
|
||||||
|
<p>The variable allows to specify the full path to a valid TLS certificate file. Available since 5.0.0.</p>
|
||||||
|
<h3 id="-zbx_db_ca_file-"><code>ZBX_DB_CA_FILE</code></h3>
|
||||||
|
<p>The variable allows to specify the full path to a valid TLS certificate authority file. Available since 5.0.0.</p>
|
||||||
|
<h3 id="-zbx_db_verify_host-"><code>ZBX_DB_VERIFY_HOST</code></h3>
|
||||||
|
<p>The variable allows to activate host verification. Available since 5.0.0.</p>
|
||||||
|
<h3 id="-zbx_sso_sp_key-"><code>ZBX_SSO_SP_KEY</code></h3>
|
||||||
|
<p>The variable allows to specify a custom file path to the Serivce Provider (SP) private key file.</p>
|
||||||
|
<h3 id="-zbx_sso_sp_cert-"><code>ZBX_SSO_SP_CERT</code></h3>
|
||||||
|
<p>The variable allows to specify a custom file path to the Serivce Provider (SP) cert file.</p>
|
||||||
|
<h3 id="-zbx_sso_idp_cert-"><code>ZBX_SSO_IDP_CERT</code></h3>
|
||||||
|
<p>The variable allows to specify a custom file path to the SAML Certificate provided by the Identity Provider (ID) file.</p>
|
||||||
|
<h2 id="-zbx_sso_settings-"><code>ZBX_SSO_SETTINGS</code></h2>
|
||||||
|
<p>The variable allows to specify custom SSO settings in JSON format. Available since 5.0.0.</p>
|
||||||
|
<p>Example of YAML Mapping to Sequences</p>
|
||||||
|
<pre><code><span class="hljs-code">....
|
||||||
|
environment:
|
||||||
|
ZBX_SSO_SETTINGS: "{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}"
|
||||||
|
....
|
||||||
|
....</span>
|
||||||
|
</code></pre><h3 id="other-variables">Other variables</h3>
|
||||||
|
<p>Additionally the image allows to specify many other environment variables listed below:</p>
|
||||||
|
<pre><code><span class="hljs-attr">ZBX_VAULTDBPATH=</span> <span class="hljs-comment"># Available since 5.2.0</span>
|
||||||
|
<span class="hljs-attr">ZBX_VAULTURL=https://127.0.0.1:8200</span> <span class="hljs-comment"># Available since 5.2.0</span>
|
||||||
|
<span class="hljs-attr">VAULT_TOKEN=</span> <span class="hljs-comment"># Available since 5.2.0</span>
|
||||||
|
|
||||||
|
Allowed PHP-FPM configuration options:
|
||||||
|
<span class="hljs-attr">PHP_FPM_PM=dynamic</span>
|
||||||
|
<span class="hljs-attr">PHP_FPM_PM_MAX_CHILDREN=50</span>
|
||||||
|
<span class="hljs-attr">PHP_FPM_PM_START_SERVERS=5</span>
|
||||||
|
<span class="hljs-attr">PHP_FPM_PM_MIN_SPARE_SERVERS=5</span>
|
||||||
|
<span class="hljs-attr">PHP_FPM_PM_MAX_SPARE_SERVERS=35</span>
|
||||||
|
<span class="hljs-attr">PHP_FPM_PM_MAX_REQUESTS=0</span>
|
||||||
|
</code></pre><h2 id="allowed-volumes-for-the-zabbix-web-interface-container">Allowed volumes for the Zabbix web interface container</h2>
|
||||||
|
<h3 id="-etc-ssl-nginx-"><code>/etc/ssl/nginx</code></h3>
|
||||||
|
<p>The volume allows to enable HTTPS for the Zabbix web interface. The volume must contains three files <code>ssl.crt</code>, <code>ssl.key</code> and <code>dhparam.pem</code> prepared for Nginx SSL connections.</p>
|
||||||
|
<p>Please follow official Nginx <a href="http://nginx.org/en/docs/http/configuring_https_servers.html">documentation</a> to get more details about how to create certificate files.</p>
|
||||||
|
<h3 id="-etc-zabbix-web-certs-"><code>/etc/zabbix/web/certs</code></h3>
|
||||||
|
<p>The volume allows to use custom certificates for SAML authentification. The volume must contains three files <code>sp.key</code>, <code>sp.crt</code> and <code>idp.crt</code>. Available since 5.0.0.</p>
|
||||||
|
<h1 id="user-feedback">User Feedback</h1>
|
||||||
|
<h2 id="documentation">Documentation</h2>
|
||||||
|
<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/6.4/Dockerfiles/web-nginx-pgsql"><code>web-nginx-pgsql/</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/6.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
|
||||||
|
<h2 id="issues">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 id="known-issues">Known issues</h3>
|
||||||
|
<h2 id="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 <a href="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>
|
||||||
Loading…
Reference in New Issue
Block a user