AgentSight and application-level tracing

Application instrumentation gives rich semantic detail when you own the code. AgentSight records the processes and effects that still matter when code is closed, hooks are incomplete, or child tools escape the application trace.

Use application traces for internal spans and domain context.

Use AgentSight for process, file, network, and resource effects.

Correlate both when one boundary cannot explain the run.

The tools answer different questions

Application spans explain instrumented control flow. A system profile explains what executed and what the process family touched. Neither boundary automatically reconstructs the other.

Combine them around a shared run

Keep framework spans when they already exist. Add AgentSight when review requires evidence about commands, files, network destinations, resource use, or closed-source components that application callbacks do not cover.

Primary sources

OpenTelemetry instrumentation concepts
AgentSight system-level recording