 Zabbix 1.8 Manualat the weekly temperatures in the server room for the last two months? Have to compare webserver load for the first month of every quarter this year? All that and more is possible with this new feature and above setups. 4.1 Performance improvements When monitoring hundreds and thousands of devices, load on the monitoring server hardware can become a serious issue. Zabbix 1.8 brings many different improvements index resolving and data retrieval is performed in a single connection now, reducing network load and load on the monitored devices. 4.2 Automated host management improvements For larger or constantly0 码力 | 485 页 | 9.28 MB | 1 年前3 Zabbix 1.8 Manualat the weekly temperatures in the server room for the last two months? Have to compare webserver load for the first month of every quarter this year? All that and more is possible with this new feature and above setups. 4.1 Performance improvements When monitoring hundreds and thousands of devices, load on the monitoring server hardware can become a serious issue. Zabbix 1.8 brings many different improvements index resolving and data retrieval is performed in a single connection now, reducing network load and load on the monitored devices. 4.2 Automated host management improvements For larger or constantly0 码力 | 485 页 | 9.28 MB | 1 年前3
 Zabbix 2.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring for OSX system.cpu.load now accepts percpu as the first parameter - if specified, total load divided by online CPU count is returned (default is still all and returns normal load value) vm.memory.size0 码力 | 791 页 | 9.66 MB | 1 年前3 Zabbix 2.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring for OSX system.cpu.load now accepts percpu as the first parameter - if specified, total load divided by online CPU count is returned (default is still all and returns normal load value) vm.memory.size0 码力 | 791 页 | 9.66 MB | 1 年前3
 Zabbix 4.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on Server X you must first create a host entry for Server X followed by an item for monitoring • Regardless of how many tabs are opened the server is polled by only one of them, reducing server load. Additionally the server response traffic is minimized, by not containing the message body and title0 码力 | 1365 页 | 16.69 MB | 1 年前3 Zabbix 4.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on Server X you must first create a host entry for Server X followed by an item for monitoring • Regardless of how many tabs are opened the server is polled by only one of them, reducing server load. Additionally the server response traffic is minimized, by not containing the message body and title0 码力 | 1365 页 | 16.69 MB | 1 年前3
 Zabbix 2.4 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring first introduced in Zabbix 2.2.3. While providing benefits in terms of reduced network traffic and load on SNMP devices, it also encountered problems with a number of devices that did not respond to these0 码力 | 910 页 | 10.81 MB | 1 年前3 Zabbix 2.4 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring first introduced in Zabbix 2.2.3. While providing benefits in terms of reduced network traffic and load on SNMP devices, it also encountered problems with a number of devices that did not respond to these0 码力 | 910 页 | 10.81 MB | 1 年前3
 Zabbix 3.2 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load off of the server. encryption - support of encrypted communications between Zabbix components (server0 码力 | 1012 页 | 12.11 MB | 1 年前3 Zabbix 3.2 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load off of the server. encryption - support of encrypted communications between Zabbix components (server0 码力 | 1012 页 | 12.11 MB | 1 年前3
 Zabbix 2.2 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring system call instead of forking a shell and running uname or hostname commands. • Reduced database load when evaluating trigger expressions containing user macros. • Zabbix server now caches global regular0 码力 | 918 页 | 11.28 MB | 1 年前3 Zabbix 2.2 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring system call instead of forking a shell and running uname or hostname commands. • Reduced database load when evaluating trigger expressions containing user macros. • Zabbix server now caches global regular0 码力 | 918 页 | 11.28 MB | 1 年前3
 Zabbix 3.4 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load off of the server. encryption - support of encrypted communications between Zabbix components (server0 码力 | 1136 页 | 15.03 MB | 1 年前3 Zabbix 3.4 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load off of the server. encryption - support of encrypted communications between Zabbix components (server0 码力 | 1136 页 | 15.03 MB | 1 年前3
 Zabbix 3.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring cache (in earlier versions directly from database). This improves performance and reduces database load. On the other hand, changing active proxy settings via frontend or API now does not have an instant0 码力 | 1074 页 | 12.04 MB | 1 年前3 Zabbix 3.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring cache (in earlier versions directly from database). This improves performance and reduces database load. On the other hand, changing active proxy settings via frontend or API now does not have an instant0 码力 | 1074 页 | 12.04 MB | 1 年前3
 Zabbix 4.2 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring • Regardless of how many tabs are opened the server is polled by only one of them, reducing server load. Additionally the server response traffic is minimized, by not containing the message body and title0 码力 | 1270 页 | 15.64 MB | 1 年前3 Zabbix 4.2 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring • Regardless of how many tabs are opened the server is polled by only one of them, reducing server load. Additionally the server response traffic is minimized, by not containing the message body and title0 码力 | 1270 页 | 15.64 MB | 1 年前3
 Zabbix 7.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on Server X you must first create a host entry for Server X followed by an item for monitoring Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load from the server. Zabbix agent - a process deployed on monitoring targets to actively monitor local0 码力 | 1949 页 | 31.91 MB | 1 年前3 Zabbix 7.0 Manualproxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server. Agent Zabbix agents are deployed on monitoring targets to actively monitor trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on Server X you must first create a host entry for Server X followed by an item for monitoring Zabbix proxy - a process that may collect data on behalf of Zabbix server, taking some processing load from the server. Zabbix agent - a process deployed on monitoring targets to actively monitor local0 码力 | 1949 页 | 31.91 MB | 1 年前3
共 26 条
- 1
- 2
- 3













