Configure Coval Trace Metrics

Create metrics from trace data only after at least one real trace exists for the target agent. If a setup-tracing validation run is currently pending, use the waiting time to inventory existing traces and prepare metric definitions. Create metrics during the wait only when historical traces or the in-flight run already prove the target span and attribute exist.

Quality bar: proof-of-ingest metrics are not the finish line. A metric that only proves traces arrived, such as generic call duration or raw span count, is diagnostic unless it answers a customer decision. Prefer metrics that expose a workflow bottleneck, user-impacting failure, dependency health issue, latency tail, cost driver, fallback, handoff, or completion signal.