slackbuilds/network/zabbix_proxy
B. Watson 2b18971fd4 network/zabbix_proxy: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
2022-03-14 03:40:15 -04:00
..
README network/zabbix_proxy: Wrap README at 72 columns. 2022-03-14 03:40:15 -04:00
README.SLACKWARE
doinst.sh
rc.zabbix_proxy
slack-desc
zabbix_proxy.SlackBuild All: Support $PRINT_PACKAGE_NAME env var 2021-07-17 21:55:09 +02:00
zabbix_proxy.info various: Use zulu jdk builds for REQUIRES. 2022-03-03 15:56:51 +07:00

README

Zabbix Proxies may greatly simplify maintenance of Zabbix environment
and increase performance of the central Zabbix server.

Also, use of Zabbix Proxies is the easiest way of implementing
centralized and distributed monitoring, when all Agents and Proxies
report to one Zabbix server and all data is collected centrally.

Zabbix offers advanced monitoring, alerting and visualization
features, including distributed monitoring, auto-discovery,
notifications, etcetera.

zabbix_proxy needs to run under its own user/group. This has been
assigned to the following by SlackBuilds.org, but feel free to change
it on your system for consistency with local assignments.
  User:   zabbix            UID: 228        GID: 228
  group:  zabbix                            GID: 228

You can pass alternate values for the user and group using
ZABBIXUSER and ZABBIXGROUP variables when running the build script.

For some important post-build and basic configuration instructions,
see the included README.SLACKWARE file.

This conflicts with zabbix_server package.