Discover env (k8s + AWS)
log10x_discover_envDiscover your Kubernetes cluster and AWS infrastructure read-only. Detects logging forwarders, Log10x apps, and metrics backends, returning a report and snapshot for install planning.
Instructions
Read-only discovery of the caller's Kubernetes cluster + AWS account: i.e. the customer's INFRASTRUCTURE environment, NOT their Log10x account. When the user wants to install Log10x: call this tool FIRST and then log10x_advise_install, that's the whole pre-flight. Do NOT call log10x_doctor / log10x_login_status / log10x_savings / etc. before the install; the wizard handles all login + license logic internally, and surfacing those tools' optional-capability warnings (Retriever, Datadog backfill, cross-pillar metrics) makes the install feel more complicated than it is. Probes kubectl (workloads, DaemonSets, Helm releases, service-account IRSA annotations, metrics-backend agents) and AWS (EKS, S3, SQS, CloudWatch log groups) to detect: which forwarder is running (Fluent Bit, Fluentd, Filebeat, Logstash, OTel Collector, Vector), which log10x apps are already installed (Reporter, Receiver, Retriever), and which metrics backends are already deployed (Datadog Agent, Prometheus, Elastic, CloudWatch Agent, etc.). Returns a terse markdown report + a snapshot_id (cached 30 min) the advisor tools consume. Do NOT call this tool to answer "which Log10x environments do I have access to" / "list my envs" / "switch envs": those are about the user's Log10x ACCOUNT environments, use log10x_login_status for that. Call THIS tool only when the question is about k8s workloads, AWS infra, or "what's deployed in my cluster". Every shell call is logged in the snapshot's probeLog for audit. No writes, no state mutation: only kubectl get and aws ... describe/list verbs. Tier prerequisites: none, this is a pre-install tool and runs against any customer environment.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | AWS region to probe. If omitted, uses the region from your AWS CLI profile. | |
| skip_aws | No | Skip all AWS probes (for cluster-only discovery). | |
| namespaces | No | Explicit list of Kubernetes namespaces to probe. If omitted, the tool auto-picks up to 5 likely candidates (demo, logging, observability, otel-demo, default) plus kube-system. | |
| bucket_hint | No | Substring to match against S3 bucket names. Defaults to "retriever"; also matches "log10x" and "tenx" out of the box. | |
| skip_kubectl | No | Skip all kubectl probes (for AWS-only discovery or when cluster access is restricted). | |
| forwarder_hint | No | Override forwarder detection. Use this if multiple forwarders are running and you want the advisor to target a specific one. | |
| namespace_hint | No | Preferred namespace for new installs. Defaults to "logging" unless an existing forwarder namespace is found. | |
| eks_cluster_name | No | EKS cluster to describe. If omitted and exactly one cluster exists in the account/region, that one is auto-selected. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| tool | Yes | ||
| view | No | summary | |
| images | No | ||
| actions | No | ||
| summary | Yes | ||
| warnings | No | ||
| truncated | No | ||
| next_cursor | No | ||
| render_hint | No | ||
| generated_at | Yes | ||
| schema_epoch | Yes | ||
| schema_version | Yes |