What problem does it solve? Investigating Kubernetes issues on Huawei Cloud CCE requires correlating Pod stdout, application logs in LTS, audit events, and control-plane logs across multiple tools and APIs, which is slow and error-prone when done manually. ## Core Features & Use Cases - Pod and Application Log Analysis: Retrieve Pod stdout/stderr (current or previous container) and query or analyze application logs collected to LTS through CCE LogConfig or LTS Access Config rules, with abnormal-ratio, incident-window, and error-pattern reporting. - Audit and Control-Plane Insight: Query CCE audit logs to find who changed or deleted resources, build resource change timelines, and analyze kube-apiserver status codes/latency and kube-scheduler scheduling, binding, and preemption failures. - Collection Rule Management: Preview and create or delete CCE LogConfig and LTS Access Config collection rules with a mandatory confirmation flow. - Use Case: A Deployment is failing after a release. Query the application's LTS logs for error spikes, check the audit timeline for who changed the workload, and analyze kube-scheduler logs for binding failures, all from one skill. ## Quick Start Ask the assistant to analyze the logs of a specific Pod or application in your CCE cluster by providing the region, cluster ID, namespace, and Pod or application name.
