/**
 * Detect metrics-backend agents running in the cluster.
 *
 * The wizard surfaces detected agents as pre-filled options for "where
 * should TenXSummary metrics go" — if the user already runs a Datadog
 * Agent, we offer Datadog as the destination so log10x metrics ride
 * alongside their existing logs/metrics on the same SIEM.
 *
 * Detection is label/name-based: each agent gets a list of matchers, and
 * we walk the cluster's helm releases + workload labels checking for a
 * hit. First match wins per kind. Confidence is graded so the wizard can
 * surface high-confidence detections prominently and treat low-confidence
 * ones as "also detected, maybe."
 *
 * Cheap probe: this all runs against data we ALREADY pulled in
 * `probeKubectl` (helm releases + the workloads we walked for forwarder
 * detection), so no additional shell calls.
 */
import type { DetectedMetricsBackend, KubectlProbes } from './types.js';
/**
 * Run the detection pass over already-pulled probe data. Walks helm
 * releases and the workload labels we have on hand (from forwarder/
 * log10x-app detection) — no extra shell calls.
 *
 * Note on input shape: we accept the FULL `KubectlProbes` rather than
 * just the bits we need so future matchers (e.g., CRD presence, IRSA
 * role arns suggesting CloudWatch) can be added without changing the
 * call site.
 */
export declare function detectBackendAgents(probes: KubectlProbes): DetectedMetricsBackend[];