Support of macros and time suffixes in time periods User macros and time suffixes (such as 30s, 5m, 2h, 1d, 1w) are now supported in item update intervals and many more locations where time periods are specified This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security requirements and mission-critical nature of server operation

This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - alert queue manager • alert syncer - alert DB writer • alerter This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-agent start Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following

has a separate configuration file. By default, these files are located in the ./zabbix_agent2.d/plugins.d/ directory. The path is specified in the Include parameter of the agent 2 configuration file and start This will work on most of GNU/Linux systems. On other systems you may need to run: /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - alert queue manager • alert syncer - alert DB writer • alerter

will work on most of GNU/Linux systems. On other systems you may need to run: 25 shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - manager of alerter tasks • alerter - process for sending This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-agent start Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following

includes: • /usr/local/etc/zabbix_server.conf.d • /usr/local/etc/zabbix_proxy.conf.d • /usr/local/etc/zabbix_agent.conf.d • /usr/local/etc/zabbix_agentd.conf.d Note: These directories are not automatically Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security requirements and mission-critical nature of server operation Display version number Windows agent only -m --multiple-agents Use multiple agent instances (with -i,-d,-s,-x functions). To distinguish service names of instances, each service name will include the Hostname

This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - manager of alerter tasks • alerter - process for sending This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-agent start Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following

This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - alert queue manager • alert syncer - alert DB writer • alerter This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-agent start Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following

This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security requirements and mission-critical nature of server operation This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-agent start Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following

This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types 27 • alert manager - alert queue manager • alert syncer - alert DB writer This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-agent start Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following

calculated using a completely custom formula, such as (A and B) and (C or D) (A and B) or (C and D) ((A or B) and C) or D etc. The formula must include all conditions (represented as uppercase letters This will work on most of GNU/Linux systems. On other systems you may need to run: shell> /etc/init.d/zabbix-server start Similarly, for stopping/restarting/viewing status, use the following commands: Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security requirements and mission-critical nature of server operation