AgentOps (tracing)
AgentOps (tracing)
AgentOps provides OpenTelemetry-backed decorators for tracing agent applications. Respan uses the spans AgentOps already creates, translates its native kinds and content into the Respan span contract, and exports them through the active Respan pipeline.
Set up Respan
Create an account at platform.respan.ai and grab an API key.
Run npx @respan/cli setup to set up with your coding agent.
Setup
Initialize and run
Initialize Respan before calling AgentOps-decorated code. You do not need to call agentops.init() or configure a second exporter.
View your trace
Open the Traces page to inspect the decorator hierarchy, inputs and outputs, and failures.
What gets traced
The integration adapts the span kinds emitted by the installed AgentOps SDK.
The adapter promotes only attributes AgentOps actually emits. It does not synthesize model, token, tool-call, or response fields for decorator kinds that do not provide them.
Content controls
Content capture is enabled by default. Disable it when decorator arguments or results may contain sensitive data:
Operation names, kinds, tags, end state, and success/error status remain available.
Lifecycle
AgentOpsInstrumentor connects AgentOps’ tracing core to the active Respan tracer provider without starting AgentOps’ exporter or metrics pipeline. activate() and deactivate() are reference-counted across instrumentor instances, and Respan retains ownership of tracer-provider shutdown.
Initialize Respan before the first decorated call. Call respan.shutdown() during application shutdown to flush pending spans and restore the prior AgentOps tracing state.