support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and by agents Flexible threshold definitions time Extensive visualization options • ability to create custom graphs that can combine multiple items into a single view • network maps • custom screens and slide shows for a dashboard-style overview secrets 9 User roles It is now possible to define user roles for granular control on what parts of UI, which API methods, and which function- ality (such as the ability to acknowledge problems) are available

support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and by agents Flexible threshold definitions and check for functionality and response time Extensive visualization options • ability to create custom graphs that can combine multiple items into a single view • network maps • slideshows in a dashboard-style global ones. Manual user input for scripts Manual user input for frontend scripts allows to supply a custom parameter on each execution of the script. This saves the necessity to create multiple similar user

support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and by agents Flexible threshold definitions and check for functionality and response time Extensive visualization options • ability to create custom graphs that can combine multiple items into a single view • network maps • slideshows in a dashboard-style *} macros supported previously. Alert script testing form has been updated to allow specifying custom parameter values for the test procedure. Interface not required for some checks It is no longer

support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and by agents Flexible threshold definitions and check for functionality and response time Extensive visualization options • ability to create custom graphs that can combine multiple items into a single view • network maps • slideshows in a dashboard-style also: • Upgrade notes • Global scripts JavaScript global scripts added Global scripts now support custom logic written in JavaScript with the ability to call external HTTP services. To configure JavaScript

support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and by agents Flexible threshold definitions time Extensive visualization options • ability to create custom graphs that can combine multiple items into a single view • network maps • custom screens and slide shows for a dashboard-style overview contents[/etc/os-release].last()} String comparison is also possible in calculated items. Test item from UI In previous Zabbix versions, it was difficult to tell if a newly-configured item was configured correctly

support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and by agents Flexible threshold definitions and check for functionality and response time Extensive visualization options • ability to create custom graphs that can combine multiple items into a single view • network maps • slideshows in a dashboard-style for virtual machine discovery, now returns additional discovery fields, including user- defined custom attribute values. The items vmware.hv.discovery[], used for hypervisor discovery, and vmware.cluster

support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and by agents Flexible threshold definitions and check for functionality and response time Extensive visualization options • ability to create custom graphs that can combine multiple items into a single view • network maps • slideshows in a dashboard-style replace the Data overview widget that is now deprecated. The Top hosts widget allows to create custom tables for data overview, which is useful for Top N-like reports and bar-progress reports useful

deploy Hubble Relay and the UI as follows on your existing installation: Installation via Helm If you installed Cilium via helm install, you may enable Hubble Relay and UI with the following command: --reuse-values \ --set hubble.listenAddress=":4244" \ --set hubble.relay.enabled=true \ --set hubble.ui.enabled=true On Cilium 1.9.1 and older, the Cilium agent pods will be restarted in the process. Installation installed Cilium 1.9.2 or newer via the provided quick-install.yaml, you may deploy Hubble Relay and UI on top of your existing installation with the following command: kubectl apply -f https://raw.githubusercontent

Observability Setting up Hubble Observability Inspecting Network Flows with the CLI Service Map & Hubble UI Network Policy Security Tutorials Identity-Aware and HTTP-Aware Policy Enforcement Locking down external pods for more details), however this is not an option on AKS clusters: It is not possible to assign custom node taints such as node.cilium.io/agent-not-ready=true:NoExecute to system node pools, cf. Azure/AKS#2578 pool created for new AKS clusters, cf. Azure/AKS#1402 [https://github.com/Azure/AKS/issues/1402]. Custom node taints on user node pools cannot be properly managed at will anymore, cf. Azure/AKS#2934 [https://github

Observability Setting up Hubble Observability Inspecting Network Flows with the CLI Service Map & Hubble UI Network Policy Security Tutorials Identity-Aware and HTTP-Aware Policy Enforcement Locking down external pods for more details), however this is not an option on AKS clusters: It is not possible to assign custom node taints such as node.cilium.io/agent-not-ready=true:NoExecute to system node pools, cf. Azure/AKS#2578 pool created for new AKS clusters, cf. Azure/AKS#1402 [https://github.com/Azure/AKS/issues/1402]. Custom node taints on user node pools cannot be properly managed at will anymore, cf. Azure/AKS#2934 [https://github