Kubernetes Intelligent Inspection¶
Based on intelligent inspection algorithms, by regularly monitoring key metrics such as the total number of Pods, Pod restarts, and API Server QPS, Kubernetes Intelligent Inspection can promptly detect and predict potential issues in the cluster. This method not only identifies abnormal fluctuations in resource usage but also precisely pinpoints the root cause through root cause analysis, whether it's configuration errors, resource mismatches, or excessive requests. This makes the operation and maintenance of Kubernetes clusters more intelligent and automated.
Use Cases¶
- In-depth insights into various performance metrics of the cluster, providing comprehensive monitoring capabilities from cluster resources, service resources to the API server level.
Configuration¶
-
Define the monitor name;
-
Select the inspection scope: Filter based on clusters, namespaces, and hosts to limit the data range for inspection. Supports adding one or more tag filters. If no filter is added, all metric data will be inspected.
View Events¶
The monitor will retrieve the metric information of the application service objects detected in the last 10 minutes. When abnormal situations are identified, corresponding events will be generated. You can view these abnormal events in the Events > Intelligent Monitoring list.
Event Details Page¶
Click Event to view the details page of the intelligent monitoring event, including event status, abnormal occurrence time, abnormal name, analysis report, alarm notifications, historical records, and related events.
-
Click Jump to Monitor in the upper right corner to view and adjust the Intelligent Monitor Configuration;
-
Click the Export button in the upper right corner, and you can choose to Export JSON File or Export PDF File to obtain all key data corresponding to the current event.
Analysis Report
-
Abnormal Summary: Displays the distribution statistics of abnormal APIServer nodes in the current cluster.
-
Abnormal Analysis: You can view information such as the number of APIServer nodes, API QPS, the number of read requests being processed, write request success rate, and the number of write requests being processed.