GOVERNATLAS / PRODUCT DOSSIER

CoreWeave Agent Lens

CoreWeave documents Agent Lens for tracing agent conversations, metrics, tool calls and errors. The page describes built-in integrations and an OpenTelemetry OTLP ingestion path; no instrumentation completeness, deployment entitlement or measured operational outcome is established.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Assess Agent Lens against a specific observability blind spot in an agent workflow. Define which conversation, tool and error events must be reconstructable before instrumenting everything. The review should establish whether the trace helps an operator explain a failure without unnecessarily retaining sensitive prompts, retrieved records or tool outputs.

What this record does not establish

The captured Agent Lens documentation supports conversation and tool-call tracing and an OTLP ingestion path. It does not establish complete instrumentation, redaction coverage or an availability commitment. Treat any legacy Weave migration as a separate compatibility review rather than assuming historical SDK behavior or shared entitlements.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

In a proposed sandbox pilot, run a multi-turn conversation with one successful tool call, one retried tool error and one cancelled turn. Compare the application's own event log with the recorded conversation and spans. If using the documented OpenTelemetry path, verify parent-child relationships, timestamps, missing spans and which semantic fields remain visible across the ingestion boundary.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A reconciled application-event and trace record identifying missing events, duplicate spans and retry behavior.
A deployment-specific record of captured fields, access permissions, retention and redaction, with migration assumptions explicitly tested.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

vendor asserted

Source, dates & preserved provenance

CoreWeave Agent Lens — official product or project documentation ↗

Authority: vendor owned
Observed 2026-10-15 · Reviewed 2026-10-15 · current until 2026-11-14

Artifact SHA-256: f57f66feeec0c229ead09f2ce7e1924acbcb3c5f976daed20ce2be0db84555df

The hash identifies the preserved capture. The live source may have changed.

Source register

CoreWeave Agent Lens — official product or project documentation ↗vendor owned · captured 2026-10-15

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

Which instrumentation and service scope applies to Agent Lens, and which historical Weave capabilities are not established as equivalent?

Can a controlled failure be traced to its source, version, owner and reviewed resolution?

Which access, retention, export and deletion evidence applies to the proposed environment?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗