LoongCollector Ops

Turn natural-language requests into executable, verifiable, rollbackable workflows for users operating their own LoongCollector and SLS resources — from install through collection to query.

Architecture: Install (ECS/self-host/ACK/self-k8s) + SLS Project + Logstore + Index + MachineGroup + Pipeline (API or ClusterAliyunPipelineConfig) + binding + SLS Lens

Scope. Covers:

• Install/upgrade Linux collector: ECS aliyun ecs run-command, self-host SSH, ACK addon loongcollector, self-k8s custom package. Must continue to collection + query; process/Addon ready is only a stage gate.
• ACK first-use: open-ack-service --type propayasgo + CS service roles (scripts/ensure_ack_prereq.sh). create-cluster only when the user asked to create a cluster. Eval hooks may pre-create a fixture cluster; that is not a production default.
• Cloud onboarding: Project / Logstore / Index / MachineGroup / Pipeline Config / binding.
• K8s collection: default SLS Pipeline API (create-logtail-pipeline-config + bind official group). CRD apply is opt-in only when the user asks for GitOps/CRD and a reachable kube-apiserver exists (references/crd-pipeline.md).
• Config management: create, modify, apply, remove, data acceptance (U1-U6).
• Machine group management: IP / user-defined identity, members, heartbeat, version.
• SLS Lens: run-log query (get-logs-v2), topic/field contracts, version routing, degradation.
• Basic troubleshooting: no-data, heartbeat abnormal.

Language and HITL Delivery Contract

Hard language rule: use the user's primary language for every user-facing message. This includes plans, clarification questions, confirmation questions and their answer options, reports, and error guidance. Product names, identifiers, CLI commands, JSON fields, error codes, and fixed status tags may remain in their original form. Never switch the surrounding prose to another language.