Zabbix is an enterprise-class open source distributed monitoring solution.
+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.
+For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com
+Zabbix server is the central process of Zabbix software.
+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.
+Images are updated when new releases are published.
+The image uses PostgreSQL database. It uses the next procedure to start:
+POSTGRES_DB database. Creating POSTGRES_DB database name if it does not existdbversion table. Creating Zabbix server database schema and upload initial data sample if no dbversion tablezabbix-server-pgsqlStart a Zabbix server container as follows:
+podman run --name some-zabbix-server-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -d zabbix/zabbix-server-pgsql:tag
+Where some-zabbix-server-pgsql is the name you want to assign to your container, some-postgres-server is IP or DNS name of PostgreSQL server, some-user is user to connect to Zabbix database on PostgreSQL server, some-password is the password to connect to PostgreSQL server and tag is the tag specifying the version you want.
++[!NOTE] +Zabbix server has possibility to execute
+fpingutility to perform ICMP checks. When containers are running in rootless mode or with specific restrictions environment, you may face errors related to fping: +fping: Operation not permitted+or +lost all packets to all resources +in this case add--cap-add=net_rawtopodman runorpodman runcommands. +Additionally fping executing in non-root environments can require sysctl modification: +net.ipv4.ping_group_range=0 1995+where 1995 iszabbixGID.
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-server-pgsql container:
$ podman exec -ti some-zabbix-server-pgsql /bin/bash
+The Zabbix server log is available through Podman's container log:
+$ podman logs some-zabbix-server-pgsql
+When you start the zabbix-server-pgsql image, you can adjust the configuration of the Zabbix server by passing one or more environment variables on the podman run command line.
DB_SERVER_HOSTThis variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'
+DB_SERVER_PORTThis variable is port of PostgreSQL server. By default, value is '5432'.
+POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_USER_FILE, POSTGRES_PASSWORD_FILEThese variables are used by Zabbix server to connect to Zabbix database. With the _FILE 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 POSTGRES_USER or POSTGRES_USER_FILE!
podman run --name some-zabbix-server-pgsql -e DB_SERVER_HOST="some-postgres-server" -v ./.POSTGRES_USER:/run/secrets/POSTGRES_USER -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -v ./.POSTGRES_PASSWORD:/run/secrets/POSTGRES_PASSWORD -e POSTGRES_PASSWORD_FILE=/var/run/secrets/POSTGRES_PASSWORD -d zabbix/zabbix-server-pgsql:tag
+With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!
+printf "zabbix" | podman secret create POSTGRES_USER -
+printf "zabbix" | podman secret create POSTGRES_PASSWORD -
+podman run --name some-zabbix-server-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -e POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD -d zabbix/zabbix-server-pgsql:tag
+By default, values for POSTGRES_USER and POSTGRES_PASSWORD are zabbix, zabbix.
POSTGRES_DBThe variable is Zabbix database name. By default, value is zabbix.
POSTGRES_USE_IMPLICIT_SEARCH_PATHIn some setups, for example including PgBouncer, setting the search_path via connection parameters fails. If this variable is set to "true", the image skips setting the search_path and trusts that the search_path of the Zabbix user is setup correctly in PostgreSQL database.
ZBX_LOADMODULEThe variable is list of comma separated loadable Zabbix modules. It works with volume /var/lib/zabbix/modules. The syntax of the variable is dummy1.so,dummy2.so.
ZBX_DEBUGLEVELThe variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_server.conf. Allowed values are listed below:
0 - basic information about starting and stopping of Zabbix processes;1 - critical information2 - error information3 - warnings4 - for debugging (produces lots of information)5 - extended debugging (produces even more information)ZBX_TIMEOUTThe variable is used to specify timeout for processing checks. By default, value is 4.
ZBX_JAVAGATEWAY_ENABLEThe variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is false.
Additionally the image allows to specify many other environment variables listed below:
+ZBX_ALLOWUNSUPPORTEDDBVERSIONS=0 # Available since 6.0.0
+ZBX_DBTLSCONNECT= # Available since 5.0.0
+ZBX_DBTLSCAFILE= # Available since 5.0.0
+ZBX_DBTLSCERTFILE= # Available since 5.0.0
+ZBX_DBTLSKEYFILE= # Available since 5.0.0
+ZBX_DBTLSCIPHER= # Available since 5.0.0
+ZBX_DBTLSCIPHER13= # Available since 5.0.0
+ZBX_VAULTDBPATH= # Available since 5.2.0
+ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
+VAULT_TOKEN= # Available since 5.2.0
+ZBX_LISTENIP=
+ZBX_LISTENPORT=10051
+ZBX_LISTENBACKLOG=
+ZBX_STARTREPORTWRITERS=0 # Available since 5.4.0
+ZBX_WEBSERVICEURL=http://zabbix-web-service:10053/report # Available since 5.4.0
+ZBX_SERVICEMANAGERSYNCFREQUENCY=60 # Available since 6.0.0
+ZBX_HISTORYSTORAGEURL= # Available since 3.4.0
+ZBX_HISTORYSTORAGETYPES=uint,dbl,str,log,text # Available since 3.4.0
+ZBX_STARTPOLLERS=5
+ZBX_IPMIPOLLERS=0
+ZBX_STARTCONNECTORS=0 # Available since 6.4.0
+ZBX_STARTPREPROCESSORS=3 # Available since 3.4.0
+ZBX_STARTPOLLERSUNREACHABLE=1
+ZBX_STARTTRAPPERS=5
+ZBX_STARTPINGERS=1
+ZBX_STARTDISCOVERERS=1
+ZBX_STARTHISTORYPOLLERS=5 # Available since 5.4.0
+ZBX_STARTHTTPPOLLERS=1
+ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
+ZBX_STARTTIMERS=1
+ZBX_STARTESCALATORS=1
+ZBX_STARTALERTERS=3 # Available since 3.4.0
+ZBX_JAVAGATEWAY=zabbix-java-gateway
+ZBX_JAVAGATEWAYPORT=10052
+ZBX_STARTJAVAPOLLERS=5
+ZBX_STARTLLDPROCESSORS=2 # Available since 4.2.0
+ZBX_STATSALLOWEDIP= # Available since 4.0.5
+ZBX_STARTVMWARECOLLECTORS=0
+ZBX_VMWAREFREQUENCY=60
+ZBX_VMWAREPERFFREQUENCY=60
+ZBX_VMWARECACHESIZE=8M
+ZBX_VMWARETIMEOUT=10
+ZBX_ENABLE_SNMP_TRAPS=false
+ZBX_SOURCEIP=
+ZBX_HOUSEKEEPINGFREQUENCY=1
+ZBX_MAXHOUSEKEEPERDELETE=5000
+ZBX_PROBLEMHOUSEKEEPINGFREQUENCY=60 # Available since 6.0.0
+ZBX_SENDERFREQUENCY=30 # Depcrecated since 3.4.0
+ZBX_CACHESIZE=8M
+ZBX_CACHEUPDATEFREQUENCY=10
+ZBX_STARTDBSYNCERS=4
+ZBX_EXPORTFILESIZE=1G # Available since 4.0.0
+ZBX_EXPORTTYPE= # Available since 5.0.10 and 5.2.6
+ZBX_AUTOHANODENAME=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
+ZBX_HANODENAME= # Available since 6.0.0
+ZBX_AUTONODEADDRESS=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
+ZBX_NODEADDRESSPORT=10051 # Allowed to use with ZBX_AUTONODEADDRESS variable only. Available since 6.0.0
+ZBX_NODEADDRESS=localhost # Available since 6.0.0
+ZBX_HISTORYCACHESIZE=16M
+ZBX_HISTORYINDEXCACHESIZE=4M
+ZBX_HISTORYSTORAGEDATEINDEX=0 # Available since 4.0.0
+ZBX_TRENDCACHESIZE=4M
+ZBX_TRENDFUNCTIONCACHESIZE=4M
+ZBX_VALUECACHESIZE=8M
+ZBX_TRAPPERTIMEOUT=300
+ZBX_UNREACHABLEPERIOD=45
+ZBX_UNAVAILABLEDELAY=60
+ZBX_UNREACHABLEDELAY=15
+ZBX_LOGSLOWQUERIES=3000
+ZBX_STARTPROXYPOLLERS=1
+ZBX_PROXYCONFIGFREQUENCY=10
+ZBX_PROXYDATAFREQUENCY=1
+ZBX_TLSCAFILE=
+ZBX_TLSCRLFILE=
+ZBX_TLSCERTFILE=
+ZBX_TLSKEYFILE=
+ZBX_TLSCIPHERALL= # Available since 4.4.7
+ZBX_TLSCIPHERALL13= # Available since 4.4.7
+ZBX_TLSCIPHERCERT= # Available since 4.4.7
+ZBX_TLSCIPHERCERT13= # Available since 4.4.7
+ZBX_TLSCIPHERPSK= # Available since 4.4.7
+ZBX_TLSCIPHERPSK13= # Available since 4.4.7
+Default values of these variables are specified after equal sign.
+The allowed variables are identical of parameters in official zabbix_server.conf. For example, ZBX_LOGSLOWQUERIES = LogSlowQueries.
Please use official documentation for zabbix_server.conf to get more information about the variables.
/usr/lib/zabbix/alertscriptsThe volume is used for custom alert scripts. It is AlertScriptsPath parameter in zabbix_server.conf.
/usr/lib/zabbix/externalscriptsThe volume is used by External checks (type of items). It is ExternalScripts parameter in zabbix_server.conf.
/var/lib/zabbix/modulesThe volume allows load additional modules and extend Zabbix server using LoadModule feature.
/var/lib/zabbix/encThe 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.
/var/lib/zabbix/ssh_keysThe volume is used as location of public and private keys for SSH checks and actions. It is SSHKeyLocation parameter in zabbix_server.conf.
/var/lib/zabbix/ssl/certsThe volume is used as location of of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_server.conf.
/var/lib/zabbix/ssl/keysThe volume is used as location of SSL private key files for client authentication. It is SSLKeyLocation parameter in zabbix_server.conf.
/var/lib/zabbix/ssl/ssl_caThe volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is SSLCALocation parameter in zabbix_server.conf.
/var/lib/zabbix/snmptrapsThe volume is used as location of snmptraps.log file. It could be shared by zabbix-snmptraps container and inherited using volumes_from Podman option while creating new instance of Zabbix server.
+SNMP traps processing feature could be enabled using shared volume and switched ZBX_ENABLE_SNMP_TRAPS environment variable to true.
/var/lib/zabbix/mibsThe volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to /var/lib/zabbix/mibs.
/var/lib/zabbix/exportDirectory for real-time export of events, history and trends in newline-delimited JSON format. Could be enabled using ZBX_EXPORTFILESIZE environment variable.
Documentation for this image is stored in the server-pgsql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
+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.
+Before you start to code, we recommend discussing your plans through a GitHub issue, 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.
diff --git a/Dockerfiles/web-nginx-pgsql/rhel/README.html b/Dockerfiles/web-nginx-pgsql/rhel/README.html new file mode 100644 index 000000000..c236cfff8 --- /dev/null +++ b/Dockerfiles/web-nginx-pgsql/rhel/README.html @@ -0,0 +1,143 @@ +
Zabbix is an enterprise-class open source distributed monitoring solution.
+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.
+For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com
+Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.
+These are the only official Zabbix web interface Podman images. Images are updated when new releases are published.
+Zabbix web interface available in four editions:
+The image based on Nginx web server with PostgreSQL database support.
+zabbix-web-nginx-pgsqlStart a Zabbix web-interface container as follows:
+podman run --name some-zabbix-web-nginx-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
+Where some-zabbix-web-nginx-pgsql is the name you want to assign to your container, some-postgres-server is IP or DNS name of PostgreSQL server, some-user is user to connect to Zabbix database on PostgreSQL server, some-password is the password to connect to PostgreSQL server, some-zabbix-server is IP or DNS name of Zabbix server or proxy, some-timezone is PHP like timezone name and tag is the tag specifying the version you want.
podman run --name some-zabbix-web-nginx-pgsql --link some-zabbix-server:zabbix-server -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
+podman run --name some-zabbix-web-nginx-pgsql --link some-postgres-server:postgres -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
+The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-web-nginx-pgsql container:
$ podman exec -ti some-zabbix-web-nginx-pgsql /bin/bash
+The Zabbix web interface log is available through Podman's container log:
+$ podman logs some-zabbix-web-nginx-pgsql
+When you start the zabbix-web-nginx-pgsql image, you can adjust the configuration of the Zabbix web interface by passing one or more environment variables on the podman run command line.
ZBX_SERVER_HOSTThis variable is IP or DNS name of Zabbix server. By default, value is zabbix-server.
ZBX_SERVER_PORTThis variable is port Zabbix server listening on. By default, value is 10051.
DB_SERVER_HOSTThis variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'
+DB_SERVER_PORTThis variable is port of PostgreSQL server. By default, value is '5432'.
+POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_USER_FILE, POSTGRES_PASSWORD_FILEThese variables are used by Zabbix web interface to connect to Zabbix database. With the _FILE 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 POSTGRES_USER or POSTGRES_USER_FILE!
podman run --name some-zabbix-web-nginx-pgsql -e DB_SERVER_HOST="some-postgres-server" -v ./.POSTGRES_USER:/run/secrets/POSTGRES_USER -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -v ./.POSTGRES_PASSWORD:/run/secrets/POSTGRES_PASSWORD -e POSTGRES_PASSWORD_FILE=/var/run/secrets/POSTGRES_PASSWORD -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
+With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!
+printf "zabbix" | podman secret create POSTGRES_USER -
+printf "zabbix" | podman secret create POSTGRES_PASSWORD -
+podman run --name some-zabbix-web-nginx-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -e POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
+By default, values for POSTGRES_USER and POSTGRES_PASSWORD are zabbix, zabbix.
POSTGRES_DBThe variable is Zabbix database name. By default, value is zabbix.
POSTGRES_USE_IMPLICIT_SEARCH_PATHIn some setups, for example including PgBouncer, setting the search_path via connection parameters fails. If this variable is set to "true", the image skips setting the search_path and trusts that the search_path of the Zabbix user is setup correctly in PostgreSQL database.
ZBX_HISTORYSTORAGEURLHistory storage HTTP[S] URL. This parameter is used for Elasticsearch setup. Available since 3.4.5.
+ZBX_HISTORYSTORAGETYPESArray 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.
+PHP_TZThe variable is timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is 'Europe/Riga' and system timezone since Zabbix 5.2.0.
ZBX_SERVER_NAMEThe variable is visible Zabbix installation name in right or left top corner of the web interface.
+DB_DOUBLE_IEEE754Use IEEE754 compatible value range for 64-bit Numeric (float) history values. Available since 5.0.0. Enabled by default.
+ENABLE_WEB_ACCESS_LOGThe variable sets the Access Log directive for Web server. By default, value corresponds to standard output.
+HTTP_INDEX_FILEThe variable controls default index page. By default, index.php.
EXPOSE_WEB_SERVER_INFOThe variable allows to hide Web server and PHP versions. By default, on.
ZBX_MAXEXECUTIONTIMEThe varable is PHP max_execution_time option. By default, value is 300.
ZBX_MEMORYLIMITThe varable is PHP memory_limit option. By default, value is 128M.
ZBX_POSTMAXSIZEThe varable is PHP post_max_size option. By default, value is 16M.
ZBX_UPLOADMAXFILESIZEThe varable is PHP upload_max_filesize option. By default, value is 2M.
ZBX_MAXINPUTTIMEThe varable is PHP max_input_time option. By default, value is 300.
ZBX_SESSION_NAMEThe variable is Zabbix frontend definition. String used as the name of the Zabbix frontend session cookie. By default, value is zbx_sessionid.
ZBX_DENY_GUI_ACCESSEnable (true) maintenance mode for Zabbix web-interface.
ZBX_GUI_ACCESS_IP_RANGEArray of IP addresses which are allowed for accessing to Zabbix web-interface during maintenance period.
+ZBX_GUI_WARNING_MSGInformation message about maintenance period for Zabbix web-interface.
+ZBX_DB_ENCRYPTIONThe variable allows to activate encryption for connections to Zabbix database. Even if no other environment variables are specified, connections will be TLS-encrypted if ZBX_DB_ENCRYPTION=true specified. Available since 5.0.0. Disabled by default.
ZBX_DB_KEY_FILEThe variable allows to specify the full path to a valid TLS key file. Available since 5.0.0.
+ZBX_DB_CERT_FILEThe variable allows to specify the full path to a valid TLS certificate file. Available since 5.0.0.
+ZBX_DB_CA_FILEThe variable allows to specify the full path to a valid TLS certificate authority file. Available since 5.0.0.
+ZBX_DB_VERIFY_HOSTThe variable allows to activate host verification. Available since 5.0.0.
+ZBX_SSO_SP_KEYThe variable allows to specify a custom file path to the Serivce Provider (SP) private key file.
+ZBX_SSO_SP_CERTThe variable allows to specify a custom file path to the Serivce Provider (SP) cert file.
+ZBX_SSO_IDP_CERTThe variable allows to specify a custom file path to the SAML Certificate provided by the Identity Provider (ID) file.
+ZBX_SSO_SETTINGSThe variable allows to specify custom SSO settings in JSON format. Available since 5.0.0.
+Example of YAML Mapping to Sequences
+....
+ environment:
+ ZBX_SSO_SETTINGS: "{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}"
+ ....
+....
+Additionally the image allows to specify many other environment variables listed below:
+ZBX_VAULTDBPATH= # Available since 5.2.0
+ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
+VAULT_TOKEN= # Available since 5.2.0
+
+Allowed PHP-FPM configuration options:
+PHP_FPM_PM=dynamic
+PHP_FPM_PM_MAX_CHILDREN=50
+PHP_FPM_PM_START_SERVERS=5
+PHP_FPM_PM_MIN_SPARE_SERVERS=5
+PHP_FPM_PM_MAX_SPARE_SERVERS=35
+PHP_FPM_PM_MAX_REQUESTS=0
+/etc/ssl/nginxThe volume allows to enable HTTPS for the Zabbix web interface. The volume must contains three files ssl.crt, ssl.key and dhparam.pem prepared for Nginx SSL connections.
Please follow official Nginx documentation to get more details about how to create certificate files.
+/etc/zabbix/web/certsThe volume allows to use custom certificates for SAML authentification. The volume must contains three files sp.key, sp.crt and idp.crt. Available since 5.0.0.
Documentation for this image is stored in the web-nginx-pgsql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
+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.
+Before you start to code, we recommend discussing your plans through a GitHub issue, 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.