Kubernetes Intelligent Inspection¶
Based on intelligent inspection algorithms, Kubernetes Intelligent Inspection regularly monitors key Metrics such as total Pods, Pod restarts, and API Server QPS, enabling timely detection and prediction of 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¶
- Deep 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 cluster, namespace, and host to limit the data range for inspection. One or more tags can be added. If no filters are added, all Metrics data will be inspected.
View Events¶
The monitor will retrieve the Metrics information of the application service objects for the last 10 minutes. When abnormal situations are identified, corresponding events will be generated. You can view the corresponding 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, alert notifications, history, 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 to support exporting JSON File and PDF File, thereby obtaining all key data corresponding to the current event.
Analysis Report
-
Exception Summary: Displays the distribution statistics of abnormal APIServer nodes in the current cluster.
-
Exception 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.