checking non-privileged user per- missions. These tables keep hashes (SHA-256) of user group sets and host group sets for each user/host respectively. Additionally, there is a permission table storing chart. Doughnut chart. For more information, see Pie chart. As part of this development, a Show aggregation function checkbox has been added to the graph widget configuration (in Legend tab). Top triggers with the highest number of problems. For more information, see: Top triggers. Time periods for aggregation in item value/top hosts widgets Time periods now can be configured in the Item value and Top hosts

export AZURE_RESOURCE_GROUP="${NAME}-group" az group create --name "${AZURE_RESOURCE_GROUP}" -l westus2 # Create AKS cluster az aks create \ --resource-group "${AZURE_RESOURCE_GROUP}" \ --name "${NAME}" the credentials to access the cluster with kubectl az aks get-credentials --resource-group "${AZURE_RESOURCE_GROUP}" -- name "${NAME}" AKS (Azure IPAM) Note Azure IPAM offers integration with the Azure export AZURE_RESOURCE_GROUP="${NAME}-group" az group create --name "${AZURE_RESOURCE_GROUP}" -l westus2 # Create AKS cluster az aks create \ --resource-group "${AZURE_RESOURCE_GROUP}" \ --name "${NAME}"

export AZURE_RESOURCE_GROUP="${NAME}-group" az group create --name "${AZURE_RESOURCE_GROUP}" -l westus2 # Create AKS cluster az aks create \ --resource-group "${AZURE_RESOURCE_GROUP}" \ --name "${NAME}" the credentials to access the cluster with kubectl az aks get-credentials --resource-group "${AZURE_RESOURCE_GROUP}" -- name "${NAME}" AKS (Azure IPAM) Note Azure IPAM offers integration with the Azure export AZURE_RESOURCE_GROUP="${NAME}-group" az group create --name "${AZURE_RESOURCE_GROUP}" -l westus2 # Create AKS cluster az aks create \ --resource-group "${AZURE_RESOURCE_GROUP}" \ --name "${NAME}"

respective forms. In a related development, in host prototype configuration the fields for host group/host group prototype selection have also been moved from a separate tab to the first tab. Subfilter in entity group (e.g. tags, hosts) up to 10 rows of entities are now displayed. If there are more entities, this list can be expanded to a maximum of 1000 entries (the value of SUBFILTER_VALUES_PER_GROUP in to 10 rows of values are displayed (expandable to 1000 entries (the value of SUBFILTER_VALUES_PER_GROUP in frontend definitions)). Audit log filter Multiple actions now can be selected in the audit log

in Zabbix, it becomes possible to select the required LDAP server for the respective user group, in user group configuration. Storage of secrets It is now possible to store some sensitive information A new subsection Template groups has been added to the Configuration menu. User role and user group permissions are now defined separately for host groups and template groups. AWS EC2 monitoring A fail on a UUID mismatch of an importable entity (host group, item, graph, etc). For example, it was not possible to import a host group if a host group with the same name already existed on the host. In

addition to automatic user creation and updating the new functionality also allows to specify user group and user media matching between LDAP/SAML and Zabbix. Provisioned users will be marked in the user the data do not match the filter. Previously such items would be ignored (no data added to the aggregation). JavaScript preprocessing The heap limit for scripts has been upped from 64 to 512 megabytes device, application, service, or any other logically-related collection of monitored parameters. host group - a logical grouping of hosts. Host groups are used when assigning access rights to hosts for different

RESOURCE_GROUP_NAME=group1 export CLUSTER_NAME=aks-test1 export LOCATION=westus az group create --name $RESOURCE_GROUP_NAME --location $LOCATION az aks create \ --resource-group $RESOURCE_GROUP_NAME \ commands to configure kubectl to connect to this AKS cluster: az aks get-credentials --resource-group $RESOURCE_GROUP_NAME --name $CLUSTER_NAME To verify, you should see AKS in the name of the nodes when you up IAM Group and User Assuming you have all the prerequisites, run the following commands to create the kops user and group: # Create IAM group named kops and grant access aws iam create-group --group-name

RESOURCE_GROUP_NAME=group1 export CLUSTER_NAME=aks-test1 export LOCATION=westus az group create --name $RESOURCE_GROUP_NAME --location $LOCATION az aks create \ --resource-group $RESOURCE_GROUP_NAME \ commands to configure kubectl to connect to this AKS cluster: az aks get-credentials --resource-group $RESOURCE_GROUP_NAME --name $CLUSTER_NAME To verify, you should see AKS in the name of the nodes when you up IAM Group and User Assuming you have all the prerequisites, run the following commands to create the kops user and group: # Create IAM group named kops and grant access aws iam create-group --group-name

RESOURCE_GROUP_NAME=aks-test export CLUSTER_NAME=aks-test export LOCATION=westeurope az group create --name $RESOURCE_GROUP_NAME --location $LOCATION az aks create \ --resource-group $RESOURCE_GROUP_NAME AZURE_NODE_RESOURCE_GROUP="$(az aks show --resource-group $RESOURCE_GROUP_NAME --name $CLUSTER_NAME | jq -r .nodeResourceGroup)" Note AZURE_NODE_RESOURCE_GROUP must be set to the resource group of the node node pool, not the resource group of the AKS cluster. Retrieve Credentials to access cluster az aks get-credentials --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME Deploy Cilium Note First

added on experimental basis in Zabbix 4.2, is now official. See also: Migration to TimescaleDB Aggregation functions in graphs Along with data display in graphs as bars, the new version also introduces values. The aggregation options are as follows: • min • max • avg • count • sum • first (first value displayed) • last (last value displayed) The most exciting use of data aggregation is the possibility comparisons of data for some period: 8 Aggregation can be configured in the data set settings when configuring a graph widget. You may pick the aggregation function and the time interval. Since a data