The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
<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 web service?</h1>
<p>Zabbix web service for performing various tasks using headless web browser (for example, reporting).</p>
<h1>Zabbix web service images</h1>
<p>Images are updated when new releases are published.</p>
<h1>How to use this image</h1>
<h2>Start zabbix-web-service</h2>
<p>Start a Zabbix web service container as follows:</p>
<p>podman run --name some-zabbix-web-service \<br />
-e ZBX_ALLOWEDIP="some-zabbix-server" --cap-add=SYS_ADMIN \<br />
-d registry.connect.redhat.com/zabbix/zabbix-web-service-62:tag</p>
<p>Where some-zabbix-web-service is the name you want to assign to your container, 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, or look at the full list of tags.</p>
<h2>Connects from Zabbix server in other containers</h2>
<p>This image exposes the standard Zabbix web service port (10053) to perform communication, so container linking makes Zabbix web service instance available to Zabbix server containers. Start your application container like this in order to link it to the Zabbix web service container:<br />
$ podman run --name some-zabbix-server \<br />
--link some-zabbix-web-service:zabbix-web-service<br />
-e ZBX_STARTREPORTWRITERS="2" -e ZBX_WEBSERVICEURL="http://some-zabbix-web-service:10053/report"<br />
-d registry.connect.redhat.com/zabbix/zabbix-server-mysql-62:latest</p>
<h2>Container shell access and viewing Zabbix web service 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-web-service container:</p>
<p>$ podman exec -ti some-zabbix-web-service /bin/bash</p>
<p>The Zabbix web service is available through Podman's container log:</p>
<p>$ podman logs some-zabbix-web-service</p>
<h2>Environment Variables</h2>
<p>When you start the zabbix-web-service image, you can adjust the configuration of the Zabbix web service by passing one or more environment variables on the <code>podman run</code> command line.</p>
<p>ZBX_ALLOWEDIP</p>
<p>This variable is IP or DNS name or list of IP / DNS names of Zabbix server. By default, value is <code>zabbix-server</code>.</p>
<p>ZBX_LISTENPORT</p>
<p>Listen port for incoming request. By default, value is <code>10053</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_web_service.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 requests. By default, value is <code>3</code>.</p>
<h3>Other variables</h3>
<p>Additionally the image allows to specify many other environment variables listed below:</p>
<p>ZBX_TLSACCEPT=unencrypted<br />
ZBX_TLSCAFILE=<br />
ZBX_TLSCERTFILE=<br />
ZBX_TLSKEYFILE=</p>
<p>Default values of these variables are specified after equal sign.</p>
<p>Please use official documentation for <a href="https://www.zabbix.com/documentation/current/manual/appendix/config/zabb..."><code>zabbix_web_service.conf</code></a> to get more information about the variables.</p>
<h2>Allowed volumes for the Zabbix web service container</h2>
<p><code>/var/lib/zabbix/enc</code></p>
<p>The volume is used to store TLS related files. These file names are specified using <code>ZBX_TLSCAFILE</code>, <code>ZBX_TLSCERTFILE</code> and <code>ZBX_TLSKEY_FILE</code> variables.</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/blob/5.4/Dockerfiles/web-service/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/trunk/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>
The following information was extracted from the containerfile and other sources.
Summary | Zabbix web service |
Description | Zabbix web service for performing various tasks using headless web browser |
Provider | Zabbix Sia |
Maintainer | alexey.pustovalov@zabbix.com |
The following information was extracted from the containerfile and other sources.
Repository name | zabbix/zabbix-web-service-62 |
Image version | 6.2 |
Architecture | amd64 |
Exposed ports | 10053:10053 |
Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.
First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.
Then, use the following from the command line or from the OpenShift Dashboard GUI interface.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running