complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components, the responsibilities of which are outlined Linux by Zabbix agent, Template OS Linux by Zabbix agent active - Linux monitored via Zabbix agent (modular) – depend on Template Module Zabbix agent, which should be imported/updated first • Template OS monitored via node exporter (monolithic) • Template OS Linux SNMPv2 - Linux monitored via SNMPv2 (modular) – depends on Template Module Generic SNMPv2, which should be imported/updated first – depends

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components, the responsibilities of which are outlined => sys- tem.stat[ent] (also on ”Dedicated” since Zabbix 3.0.23) system.sw.arch Software architecture information. String Example: => system.sw.arch → i686 Info is acquired from uname() function symbols and extra spaces. Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture. 177 Key system.uptime System uptime in seconds. Integer In item

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components, the responsibilities of which are outlined => sys- tem.stat[ent] (also on ”Dedicated” since Zabbix 3.4.15) system.sw.arch Software architecture information. String Example: => system.sw.arch → i686 Info is acquired from uname() function symbols and extra spaces. Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture. 162 Key system.uptime System uptime in seconds. Integer In item

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components, the responsibilities of which are outlined disk/tape (float) This item is supported since Zabbix 1.8.1. 143 Key system.sw.arch Software architecture information. String Example: => system.sw.arch → i686 Info is acquired from uname() function symbols and extra spaces. Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture. 148 Key system.uptime System uptime in seconds. Integer In item

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components. Their responsibilities are outlined below trigger + 1 graph
2 Example with Amazon general purpose EC2 instances, using ARM64 or x86_64 architecture, a proper instance type like Compute/Memory/Storage optimised should be selected during Zabbix file.cksum produced different sha256 sums for the same file depending on the platform (processor architecture) – sha256 sums on AIX, HP-UX (Itanium) and Solaris (SPARC) differed from those produced on Intel

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components. Their responsibilities are outlined below Processes Multithreading Several changes have been made as part of transitioning to a multithreaded architecture: • A new configure parameter has been added: --with-stacksize. This parameter allows to override trigger + 1 graph
2 Example with Amazon general purpose EC2 instances, using ARM64 or x86_64 architecture, a proper instance type like Compute/Memory/Storage optimised should be selected during Zabbix

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components. Their responsibilities are outlined below => sys- tem.stat[ent] (also on ”Dedicated” since Zabbix 4.0.1) system.sw.arch Software architecture information. String Example: => system.sw.arch → i686 Info is acquired from uname() function symbols and extra spaces. Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture. 208 Key system.uptime System uptime in seconds. Integer In item

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components, the responsibilities of which are outlined stat[ent] - supported on AIX LPAR of type ”Shared” and ”Dedicated” system.sw.arch Software architecture information. String Example: => system.sw.arch → i686 Info is acquired from uname() function symbols and extra spaces. Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture. 186 Key system.uptime System uptime in seconds. Integer In item

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components, the responsibilities of which are outlined (float) This item is supported starting from version 1.8.1. 136 Key system.sw.arch Software architecture information. String Example: system.sw.arch i686 Info is acquired from uname() function define their own types of discovery, provided they follow a particular JSON protocol. The general architecture of the discovery process is as follows. First, a user creates a discovery rule in ”Configuration”

complex environments • remote monitoring made easy by using a Zabbix proxy 4 Zabbix overview Architecture Zabbix consists of several major software components. Their responsibilities are outlined below trigger + 1 graph
2 Example with Amazon general purpose EC2 instances, using ARM64 or x86_64 architecture, a proper instance type like Compute/Memory/Storage optimised should be selected during Zabbix file.cksum produced different sha256 sums for the same file depending on the platform (processor architecture) – sha256 sums on AIX, HP-UX (Itanium) and Solaris (SPARC) differed from those produced on Intel