monitoring item keys. 5.17 Context support in user macros An optional context can be specified in user macros - {$MACRO:context}. This allows to override the default macro value by a context specific one. If there there are no values defined for the specified macro context then macro will resolve to its default value (the one defined for the same macro without context). For more information, see user macros documentation zero. 5.20.2 Configuration parameters Default configuration files have been changed to improve security and usability. • DBUser has been changed to zabbix for proxy and server • Default value for MaxHousekeeperDelete

fields for the required host parameters (host address, port, proxy name/no proxy). These fields are context aware: 10 • The values are pre-filled when possible, i.e. for items requiring an agent, by taking have to be filled manually for template items • The fields are disabled when not needed in the context of the item type (e.g. the host address field is disabled for calculated and aggregate items, the Screenshots of Graph widget and Graph (classic) widget can now be downloaded as .png files from the widget context menu. Filtering problems by severities in Monitoring→Problems Problems displayed in the Monitoring→

can be used in item preprocessing steps for item prototypes. User macros and user macros with context can be used in item preprocessing steps for regular items and item prototypes. Substring extraction Triggers (in the new Value column), while trigger descriptions can be accessed from the Trigger context menu and are opened in a popup window. Inventory macro support in event tags {INVENTORY.*} macros be opened, worked with and closed by keyboard; • Context menu options can now be navigated by keyboard arrows. Pressing Esc will close the whole context menu, while pressing Enter will activate the selected

when testing SNMP items, problems are often associated with a wrong SNMPv2 community or SNMPv3 security credentials. The values of these fields are pre-filled by the values of the corresponding SNMP number of failed login attempts and period of blocking login page after exceeding this limit; – Security, which allows to set URI scheme validation rules, X-Frame-Options HTTP header, and custom iframe components (server, proxy, agent, zabbix_sender and zabbix_get utilities) using Transport Layer Security (TLS) protocol. network discovery - automated discovery of network devices. low-level discovery

with the actual/recommended values, i.e. SMTP server, SMTP server port, SMTP helo, and Connection security. Because of this automation, these fields are not even shown, however, it is possible to see the maximum length of the HostMetadata option in agent configuration has been increased to 2034 bytes. Security Secure password change When changing your user password in User profile or User configuration (for password can only be changed for users using Zabbix internal authentication. CSRF tokens For enhanced security against CSRF (Cross Site Request Forgery) attacks, Zabbix frontend now uses randomly generated CSRF

timeframe in multiple equal time periods (’sea- sons’) using the weighted moving average algorithm. In context of these functions, the term ’season’ refers to a configurable timeframe, which could be hours, days Anomaly detection algorithms do exactly this - find data that doesn’t look normal (outliers) in a context of other values. New trend function trendstl() has been added which uses ’decomposition’ method configuration and latest data A new context menu for items has been introduced in Latest data allowing to access the item configuration and available graphs: Conversely, a new context menu has been introduced in

tag for matching) now may include user macros and user macro context. Low-level discovery macros can be used inside the user macro context. Additionally, the limitation of using a ’/’ forward slash has 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, UNIX is the only operating system components (server, proxy, agent, zabbix_sender and zabbix_get utilities) using Transport Layer Security (TLS) protocol. 3 Agent Overview Zabbix agent is deployed on a monitoring target to actively

components (server, proxy, agent, zabbix_sender and zabbix_get utilities) using Transport Layer Security (TLS) protocol. 27 network discovery - automated discovery of network devices. low-level discovery 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, UNIX is the only operating system recommended to run the database on a separate box for large installations. Supported platforms Due to security requirements and mission-critical nature of monitoring server, UNIX is the only operating system

components (server, proxy, agent, zabbix_sender and zabbix_get utilities) using Transport Layer Security (TLS) protocol. network discovery - automated discovery of network devices. low-level discovery using the zabbix[process,,,] internal item. Supported platforms Due to the security requirements and mission-critical nature of server operation, UNIX is the only operating system recommended to run the database on a separate box for large installations. Supported platforms Due to security requirements and mission-critical nature of monitoring server, UNIX is the only operating system

now available for out-of-the-box monitoring: 19 • Cisco ASAv SNMP - monitoring of Cisco Adaptive Security Virtual Appliance (ASAv) via SNMP; • Cloudflare by HTTP - monitoring of Cloudflare web traffic information, see getHeaders() in Additional JavaScript objects. Security Vulnerability to CVE-2021-42550 has been fixed. As an additional security measure it is recommended to check permis- sions to the / components (server, proxy, agent, zabbix_sender and zabbix_get utilities) using Transport Layer Security (TLS) protocol. network discovery - automated discovery of network devices. low-level discovery