ID |
sls_app_audit_dataflow_at_ingress_latency |
Name |
K8s Ingress Average Request Latency Too High Alert |
Version |
1 |
Type |
Cloud Platform, Alicloud, Data Security, and K8s Flow Security |
Usage |
Monitors the average request latency of Kubernetes Ingress. If the latency is higher
than the specified threshold, an alert is triggered.
|
Check Frequency |
Fixed interval: 1 minute. |
Time Range |
The data of the last 2 minutes is checked. |
Parameter Settings |
You can specify the following parameters:
- Alert Name: The name of the alert. You can create multiple alerts.
- Severity: The severity level of the alert. Valid values: Critical-10, High-8, Medium-6, Low-4,
and Report-2.
- Threshold: The threshold for the average request latency of Kubernetes Ingress. Default value:
200. Units: milliseconds. If the average latency exceeds the threshold within 2 minutes,
an alert is triggered.
- Account ID (Aliuid): The ID of the Alibaba Cloud account that you want to monitor. You can use regular
expressions when you specify this parameter.
- You can separate multiple IDs with vertical bars (|). You can also use wildcards for
the regular expressions, such as
.* . For example, 156133.* indicates that Alibaba Cloud accounts that start with 156133
are monitored.
- Default value:
.* . This indicates all Alibaba Cloud accounts configured in the Log Audit Service application
are monitored.
- K8s Cluster Name: The name of the Kubernetes cluster to be monitored. You can use regular expressions
when you specify this parameter.
- You can also use wildcards for the regular expressions, such as
.* .
- Default value:
.* . This indicates all Kubernetes clusters of the specified Alibaba Cloud account are
monitored.
|
External Configurations |
None. |
Solution |
Check whether an exception occurs in the Kubernetes cluster that triggered the alert.
|
Prerequisites |
The Ingress Log switch of Kubernetes is turned on. To turn on the switch, go to the Log Audit Service
console, and then choose .
|