a web-based frontend in PHP • accessible from anywhere • you can click your way through • audit log Zabbix API • Zabbix API provides programmable interface to Zabbix for mass manipulations, 3rd party turn unsupported and the global refresh interval has been set to a short value. Macros • {ITEM.LOG.*} macros are now also supported in: – trigger names, operational data, URLs and descriptions; – number). • Zabbix agent for Windows now substitutes SIDs with account name and domain name in event log messages. 9 What’s new in Zabbix 5.2.4 Testing preprocessing steps It is now possible to test item

a web-based frontend in PHP • accessible from anywhere • you can click your way through • audit log Zabbix API • Zabbix API provides programmable interface to Zabbix for mass manipulations, third-party new read- write lock. This reduces locking between history syncers, trappers and proxy pollers by using a shared read lock while accessing the configuration cache. The new lock can be write locked only preprocessing have been intro- duced: • The total size of all messages that can be logged with the log() method has been limited to 8 MB per script execution. • The initialization of multiple HttpRequest

a web-based frontend in PHP • accessible from anywhere • you can click your way through • audit log Zabbix API • Zabbix API provides programmable interface to Zabbix for mass manipulations, third-party functions abs, acos, asin, atan, atan2, cbrt, ceil, cos, cosh, cot, degrees, e, exp, expm1, floor, log, log10, mod, pi, power, radians, rand, round, signum, sin, sinh, sqrt, tan, truncate Operator functions Methods also have been renamed for greater consistency with JavaScript: New naming Old naming log Log addHeader AddHeader clearHeader ClearHeader getHeaders GetHeaders get Get put Put post Post

theming guide. 9. Q: With DebugLevel 4 I’m seeing messages ”Trapper got [] len 0” in server/proxy log - what’s that? A: Most likely that is frontend, connecting and checking whether server is still running objects in ORCL service located on the host Oracle database server with a user shell user having write access to /tmp directory. Zabbix requires a Unicode database character set and a UTF8 national character to be sent to the history storage. # # Mandatory: no # Default: # HistoryStorageTypes=uint,dbl,str,log,text 用于设置 Zabbix server 配置文件的示例参数值如下：Example parameter values to fill the Zabbix server configuration

Default: # HistoryStorageTypes=uint,dbl,str,log,text 例如使用以下示例参数值，来设置 Zabbix server 的配置文件： HistoryStorageURL=http://test.elasticsearch.lan:9200 HistoryStorageTypes=str,log,text 使用此配置，Zabbix server 会将数值类型的历史 dbl,str,log,text 支持的监控项类型说明： Item value type Database table Elasticsearch type Numeric (unsigned) history_uint uint Numeric (float) history dbl Character history_str str Log history_log log Text history_text 前端的配置文件： $HISTORY['url'] = 'http://test.elasticsearch.lan:9200'; $HISTORY['types'] = ['str', 'text', 'log']; 使用此配置，文本、字符和日志类型的历史数据将存储到 Elasticsearch 中。 您 还 需 要 将 conf/zabbix.conf.php 文 件 的 中 $HISTORY 配 置

组合字符串和值，或将两个或多个值相互附加。还支持数字数据类 型。 监控项 自动类型选择 监控项配置表单会自动建议匹配的信息类型，如果选定的监控项键值仅返回特定类型的数据（例如，log[] 监控行需要信息类型：Log）。 信息类型 * 参数现在位于监控项选项卡上的键值参数下，如果指定了至少一个预处理步骤，则在预处理选项卡上重复。如果 Zabbix 检测 到所选信息类型和密钥可能不匹配，则会在 信息类型字段旁边显示一个警告图标。 了多个日志记录，则这些记录 将具有相同的 Recordset ID。 审计设置 新的 Audit log 部分 已添加到 Administration→General 菜单，允许启用或禁用审计日志。以前位于 Housekeeper 部分下的用于审核的管 家设置也已移至新的 Audit log 部分。 PCRE2 支持 已添加对 PCRE2 的支持，并且针对 RHEL/CentOS 7 及更高 preprocessing have been intro- duced: • The total size of all messages that can be logged with the Log() method has been limited to 8 MB per script execution. • The initialization of multiple HttpRequest

a web-based frontend in PHP • accessible from anywhere • you can click your way through • audit log Zabbix API • Zabbix API provides programmable interface to Zabbix for mass manipulations, third-party been renamed to Audit log under Reports. • The Administration menu no longer contains submenus related to alerting and user management. Also: • Housekeeping, Macros and Audit log that previously were option is now checked by default. Action log export to CSV It is now possible to export action log records to a CSV file. For more information, see Action log. Higher limit for host metadata The HostMetadataItem

a web-based frontend in PHP • accessible from anywhere • you can click your way through • audit log Zabbix API • Zabbix API provides programmable interface to Zabbix for mass manipulations, third-party (with trapping enabled). In addition, correct history.push operations are recorded in Reports → Audit log that has additional filtering options (a new Push action and History resource), and the history.push in Windows event log A new eventlog.count item has been added to Zabbix agent/agent 2 on Windows. This item returns an integer value with the count of lines in the Windows event log based on the specified

a web-based frontend in PHP • accessible from anywhere • you can click your way through • audit log Zabbix API • Zabbix API provides programmable interface to Zabbix for mass manipulations, third-party services. Permissions Flexible permissions to services have been implemented on user role level. Read-write or read-only access can be granted to all, none or selected services (based on name or tags). Root information, if selected item key returns data only of the specific type (for example, log[] item requires Type of information: Log). Type of information parameter is now located under the Key parameter on the

a web-based frontend in PHP • accessible from anywhere • you can click your way through • audit log Zabbix API • Zabbix API provides programmable interface to Zabbix for mass manipulations, third-party severity level available. Webhook media type test usability improved It is now possible to view log entries during a webhook media type test. Miscellaneous • The latest data page no longer displays Remote command logging, if enabled on Zabbix agent/agent2 (LogRemoteCommands=1) will no longer create log entries for sys- tem.run[] if it is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem