Install

Scan, recommend, install. Returns paste-ready Helm commands. Nothing in Log10x needs to be running yet.

"scan env for install candidates"

Detected: fluent-bit DaemonSet (3 replicas) · EKS 1.28 · S3 bucket logs-archive · 2 forwarders, no Helm conflicts.

"recommend install path"

Top pick: Reporter (standalone DaemonSet) — no forwarder changes required. Alternatives ranked: Reducer inline, Retriever.

"Reporter plan, fluent-bit, mock destination"

helm upgrade --install my-reporter log10x/fluent-bit-10x \
  --namespace logging --set log10x.apiKey=lx_live_... \
  --set log10x.destination=mock
kubectl -n logging rollout status ds/my-reporter

Plus matching verify probes and a helm uninstall teardown.

You ask	Example answer
scan environment for install candidates	Detected: fluent-bit DaemonSet (3 replicas) · EKS 1.28 · AWS account 123456 · S3 bucket logs-archive · 2 forwarders, no Helm conflicts
recommend install path for snap-abc123	Top pick: Reporter (standalone DaemonSet) — no forwarder changes required. Alternatives ranked: Reducer inline, Retriever
Reporter plan, fluent-bit, mock destination	Helm values + install/verify/teardown commands. Inline (modify forwarder chart) or standalone (parallel DaemonSet)
Reducer plan, optimize=true	Same shape as Reporter, with the Compact mode option (~20–40× volume reduction)
Retriever plan	Helm + Terraform plan for the S3-backed archive. Events stay in the customer AWS account.
PR to compact payment_retry, hot-reload	A gh PR command + diff for a Compact mode lookup-CSV update against the customer GitOps repo. Engine hot-reloads — no pipeline restart.

Prerequisites

kubectl and/or aws CLI with credentials. Either is optional — missing tools are reported and the advisors fall back to asking. Nothing in Log10x needs to be running yet; these tools generate plans, they don't execute anything.