. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 17 Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . takes into account reserved diskspace for root user. • Comment at the end of a configuration file line is not allowed anymore (this worked for numeric parameters only before). 3.3.2 For version 1.8.3 97: Address family not supported by protocol. 3.3.3 For version 1.8.5 • The method of external command invocation for Zabbix daemons has been changed to allow terminating runaway processes. Instead of

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057 9 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption support Network communications between Zabbix components (server, proxies, agents and command-line utilities) can now be encrypted if Zabbix is compiled with mbed TLS (PolarSSL), GnuTLS or OpenSSL library passed to custom alert scripts - Send to, Subject and Message. Now users can define their own command-line parameters for the script in the media type configuration form: 10 Additionally, three new macros

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1350 10 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Previously in event details there were separate blocks for acknowledgments, message and remote command actions. Now all activities on the problem are displayed in one block and symbolic icons are used accepted without validation for duplicate values, ensuring backwards compatibility. Miscellaneous • Command line arguments that exceed 2KB are now supported in proc.num and proc.mem checks on AIX platform.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541 10 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . zabbix_sender -z 127.0.0.1 --with-timestamps --with-ns -i values.txt This option specifies that each line of the input file contains the following, whitespace-delimited: • The list of web scenario HTTP user agents has been updated. Daemons Remote command logging on agent Remote command logging, if enabled on Zabbix agent/agent2 (LogRemoteCommands=1) will no longer

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117 10 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . network devices. For more information, see: • Standardized templates for network devices 3 Remote command support through proxies Remote commands and global scripts previously could not be executed by Zabbix proxy itself - the command was always executed by the server. In Zabbix 3.4, remote commands and global scripts are correctly executed on hosts monitored by proxies. The command is executed by the agent

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995 2 9 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . these: Line1: Application 1 stopped Line2: Application 2 stopped Line3: Application 1 was restarted Line4: Application 2 was restarted With event correlation, you can match the problem event from Line1 to from Line3 and the problem event from Line2 to the resolution from Line4, and close these problems one by one: Line1: Application 1 stopped Line3: Application 1 was restarted #problem from Line 1 closed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1657 10 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . configure two types of actions: sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem escalation scenarios userparameter_reload UserParameter is the only agent configuration option that will be reloaded with this command. PCRE2 support Support for PCRE2 has been added and Zabbix installation packages for RHEL 7 and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714 10 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . change its working directory to the one specified by this parameter before executing a UserParameter command. Thereby UserParameter commands can have a relative ./ prefix instead of a full path. Example: which can be used to set additional properties in such a way that they are not visible on a command line or to overwrite existing ones. Zabbix agent 2 plugins Parameter structure for Zabbix agent 2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1800 10 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • manual event action ’Manual event action’ here is another new feature, allowing to execute a command from the event menu. This feature may be handy for running scripts used for managing problem tickets notification - a message about some event sent to a user via the chosen media channel. remote command - a pre-defined command that is automatically executed on a monitored host upon some condition. template -

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370 11 Command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . when notification sounds on the device cannot be played. Monospaced fonts in trigger expression/command fields For better readability, text area fonts have been changed to monospace in the following locations: Formula field of calculated items • SQL query field of database monitor items • Command field of global scripts • Remote command field in action configuration Longer input fields Input fields that potentially