skills.rest
pancake0001
pancake0001COMMUNITY
Explore all skills by this author →
GitHub

huawei-cloud-cce-observability-context-builder

Collects read-only Kubernetes, alarm, metric, and log evidence into a CCE incident context package.

1|Updated May 27, 2026
Search Tags:#kubernetes#observability#kubectl#alarms#incident-triage#cce#huawei-cloud
One-click install
npx skills add https://github.com/pancake0001/huawei-cloudnative-skills --skill huawei-cloud-cce-observability-context-builder-pancake0001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: huawei-cloud-cce-observability-context-builder
Source: https://github.com/pancake0001/huawei-cloudnative-skills/tree/main/releases/container/cce/huawei-cloud-cce-observability-context-builder
Command: npx skills add https://github.com/pancake0001/huawei-cloudnative-skills --skill huawei-cloud-cce-observability-context-builder-pancake0001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a Huawei Cloud CCE incident occurs, engineers waste time manually gathering cluster state, Events, Pod logs, AOM alarms, and metrics from scattered tools before diagnosis can even begin. This Skill builds a unified, read-only observability context package so root-cause analysis starts from a shared timeline, scope, and evidence set. ## Core Features & Use Cases - Cluster and inventory context: Resolves and validates the target CCE cluster via hcloud (ListClusters, ShowCluster, ListNodes) with strict region and cluster_id validation. - Kubernetes state collection: Uses the kubectl-cce plugin to gather Pods, workloads, Services, Ingresses, Nodes, PVCs, Events, and bounded Pod logs. - Signal normalization and handoff: Merges alarms, metrics, Events, and logs from dedicated analyzer skills into one timeline, records data gaps, and recommends the next diagnoser. - Use Case: A user reports a failing deployment in a CCE cluster. The Skill collects the last hour of Events, Pod logs, alarms, and metrics, then outputs a Markdown context package with a recommended handoff to the workload failure diagnoser. ## Quick Start Build an observability context package for my CCE cluster in region cn-north-4 covering the last hour of pod failures in the default namespace.

Frequently Asked Questions about huawei-cloud-cce-observability-context-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect CCE incident context before root-cause diagnosis?▼

Provide the region, cluster_id, and an optional time window or symptom. The Skill validates the cluster via hcloud, gathers Kubernetes state and Events with kubectl cce, pulls alarms and metrics from analyzer skills, and outputs a Markdown context package with a recommended next diagnoser.

What tools are required to query Huawei Cloud CCE cluster state?▼

You need the hcloud CLI, kubectl, and the kubectl-cce plugin installed as platform-native binaries. If any tool is missing, use the huawei-cloud-kubectl-cce-installer skill; this Skill never downloads installers or falls back to SDK or kubeconfig access.

Can I use a cluster name instead of a cluster UUID?▼

Yes, but only if the name resolves to exactly one cluster. The Skill lists CCE clusters, performs an exact name match, converts it to a UUID, and verifies it with ShowCluster. Ambiguous or unmatched names stop the operation and require a UUID.

Does this Skill modify my Kubernetes cluster or cloud resources?▼

No. It is strictly read-only: it runs discovery, log, event, metric, and alarm queries only. Mutation commands like apply, delete, scale, drain, or reboot are explicitly forbidden, and log collection is bounded with --tail limits.

Why does the context package report data gaps?▼

Data gaps appear when sources like AOM, LTS, Metrics API, or previous container logs are unavailable due to RBAC, restarts, or plugin limits. The Skill records the source, failure reason, and confidence impact instead of treating missing evidence as healthy.

What happens when kubectl cce returns an x509 certificate error?▼

Retry the same command with --cce-insecure-upstream-tls=true placed immediately after cce. This flag is used only when that specific TLS validation error occurs, not as a default.

Related Skills

Explore More Software Engineering Skills→
nimranaz148nimranaz148

kubectl-ai

Generate and modify Kubernetes resources from natural language prompts.

Community
Advanced
david-driscolldavid-driscoll
1

sre

Diagnose Kubernetes incidents via triage, evidence collection, and 5 Whys root cause analysis.

Community
Advanced
githubgithub
38.5k

aws-cloudwatch-investigation

Provides CloudWatch Logs Insights queries and metric patterns for structured incident triage.

Official
Intermediate
prince3626ezechiel-langprince3626ezechiel-lang

huawei-cloud-billing-scout

Query Huawei Cloud BSS balance, spend, and billing data read-only.

Community
Intermediate