Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_zabbix_monitoring [2018/03/08 19:28] – [Zabbix Version Compatibility] abelbeck
+++ userdoc:tt_zabbix_monitoring [2018/03/08 20:07] (current) – [Zabbix Version Compatibility] abelbeck
@@ Line 5: / Line 5: @@
 The zabbix_agentd and zabbix_proxy daemons //(in AstLinux)// are relatively small, headless, and efficient using the compiled 'C' language.  Their purpose is to collect data and communicate upstream to the zabbix_server //(not in AstLinux)//, which utilizes a production database and provides the web interface for reports and graphs.
-The zabbix_server must be configured and maintained separately from AstLinux.  A good starting point is the **Zabbix Appliance** which can be found on the [[http://www.zabbix.com/download.php#appliance|Zabbix Downloads]] page.  Installing the Zabbix Appliance in a Virtual Machine is a great way to learn Zabbix and possibly manage a small number of AstLinux boxes.  Unfortunately, upgrading a Zabbix Appliance to a newer version is not as simple as it should be.  Installing Zabbix from it's parts on a CentOS or Debian/Ubuntu distribution may be a better choice for some.
+The zabbix_server must be configured and maintained separately from AstLinux.  A good starting point is the **Zabbix Appliance** which can be found on the [[https://www.zabbix.com/download_appliance|Zabbix Downloads]] page.  Installing the Zabbix Appliance in a Virtual Machine is a great way to learn Zabbix and possibly manage a small number of AstLinux boxes.  Unfortunately, upgrading a Zabbix Appliance to a newer version is not as simple as it should be.  Installing Zabbix from it's parts on a CentOS or Debian/Ubuntu distribution may be a better choice for some.
-It should be clear that deploying a Zabbix monitoring solution is not for the solo AstLinux user.  Though if you are responsible for many AstLinux boxes at many locations, configuring and maintaining Zabbix is well worth the effort.
+It should be clear that deploying a Zabbix monitoring solution is not for the solo AstLinux user.  Though if you are responsible for many AstLinux boxes at many locations, configuring and maintaining Zabbix can be well worth the effort.
 !!Note: AstLinux 1.0.5 or later is required!!
+!!Note: AstLinux 1.3.3 or later includes Zabbix 3.0 LTS!!
 ==== Zabbix Version Compatibility ====
@@ Line 18: / Line 20: @@
 !!Tip ->!! Before upgrading AstLinux be sure to see if your zabbix_server version is in the same series or newer than what the latest AstLinux includes.  You may need to first, migrate your zabbix_server to a newer version.
+!!Note ->!! AstLinux 1.3.3 or later requires a zabbix_server using Zabbix 3.0 or later.
 Be sure to check the [[https://www.zabbix.com/documentation/3.0/|Zabbix Documentation]] page for version specific details.
@@ Line 61: / Line 65: @@
 ==== Encryption via Stunnel ====
-Currently, Zabbix does not provide native support for encryption or certificate authentication for the zabbix_agentd or zabbix_proxy data streams.  If the cleartext data that Zabbix exchanges with the server contains information that you don't want to share with the public internet, some sort of SSL wrapper is required.  Using OpenVPN is one choice, but a simpler solution in this case is to use "stunnel".
+Zabbix 3.0 or later supports encrypted communications between Zabbix server, Zabbix proxy and Zabbix agent using Transport Layer Security (TLS) protocol v.1.2.
+AstLinux 1.3.3 or later users may continue to use "stunnel" as outlined below, though new configurations should look at the native encryption support described here:
+[[https://www.zabbix.com/documentation/3.0/manual/encryption|Zabbix 3.0 Encryption]]
+Earlier versions of Zabbix did not provide native support for encryption or certificate authentication for the zabbix_agentd or zabbix_proxy data streams.  If the cleartext data that Zabbix exchanges with the server contains information that you don't want to share with the public internet, some sort of SSL wrapper is required.  Using OpenVPN is one choice, but a simpler solution in this case is to use "stunnel".
 The example below demonstrates how to use stunnel to encrypt the zabbix_proxy connection to the Zabbix server, while the zabbix_agentd is also routed via the zabbix_proxy connection.