Environment:
Version 7.0.10 (LTS)
With the agents on the servers configured towards the proxies, data points such as Value/Trend cache/cluster data was reporting as "no data" (invalid first parameter). After reading this (8 Internal checks) and configuring the agents to be monitored by the servers themselves, this missing data became available. However, we noticed process values per second pretty much double in the Zabbix Server Health dashboard. Which leads to more question than answers.
Ignoring the doubled VPS as a result of changing the "monitored by" for the Zabbix servers, should the "standby" server node be showing 0 values per second or should it be displaying a VPS value similar to that of the active node? In the environment, the standby Zabbix server is also showing values per second similar to that of the active Zabbix server.
Regards
Version 7.0.10 (LTS)
- 2 x Proxies in a Proxy Group (ActiveChecks) (zabbix proxy template)
- 2 x Zabbix Servers in a HA Cluster (Active/Standby) (ActiveChecks) (zabbix server template)
- Agents configured to proxies, including the agents installed on the Zabbix servers (initially).
With the agents on the servers configured towards the proxies, data points such as Value/Trend cache/cluster data was reporting as "no data" (invalid first parameter). After reading this (8 Internal checks) and configuring the agents to be monitored by the servers themselves, this missing data became available. However, we noticed process values per second pretty much double in the Zabbix Server Health dashboard. Which leads to more question than answers.
Ignoring the doubled VPS as a result of changing the "monitored by" for the Zabbix servers, should the "standby" server node be showing 0 values per second or should it be displaying a VPS value similar to that of the active node? In the environment, the standby Zabbix server is also showing values per second similar to that of the active Zabbix server.
Regards