Skip to main content
Coverage describes the delivery contract, not every version of a third-party package. Use this page to find the recommended tracing path for a framework or library, then follow its guide.

Tracing libraries

Agent frameworks

Run one representative request after every framework or instrumentor upgrade. Confirm the root, provider call, tool calls, usage, and expected parent relationships in Agent Registry before promoting the build.

Evaluation trace joins

Third-party spans created inside an Eval task inherit atlan.eval.experiment_id, atlan.eval.case_id, and, for a dataset-backed case, atlan.eval.dataset_record_id from the active context. The experiment result then stores the root trace_id of the case. Bench filters use the experiment attribute, and case drill-down uses the result-to-trace join. If you run your own harness, execute it inside run.trace() in Python or propagateAttributes(run.traceOptions, fn) in TypeScript. Flush and verify the traces, upload complete result rows with their numeric score snapshots, then mark the experiment completed with one update. Read the returned experiment’s summary; no separate summarize request is needed.

See also