Integrations

Choose the Judgment integration that matches how your application creates and exports traces.

Choose one primary instrumentation path:

• Use a framework integration when your agent framework is listed below.
• Use a model-provider integration when your application calls that model client directly and no framework integration already captures the call.
• Use an OpenTelemetry export when your application already emits spans.

After setup, run one real agent path and verify the resulting trace. Add custom attributes only after the basic trace is complete.

Framework auto-instrumentation

Start here when your application uses a supported agent framework. These guides capture the framework’s agent steps, model calls, and tool calls with minimal changes to your application.

Model-provider instrumentation

Choose a provider guide when your application calls a supported model client directly. Provider instrumentation captures model requests, responses, token usage, and other available model metadata.

Direct or dual OTEL export

Use Direct OTEL when Judgment is your trace destination. Use Dual Export when the same spans must also reach another OpenTelemetry-compatible backend.

If your application already uses one of these tracing libraries, keep that instrumentation and configure its OpenTelemetry export path for Judgment:

Other runtime and library instrumentation

Use standard OpenTelemetry instrumentation to capture supporting work in web frameworks, HTTP clients, databases, queues, and serverless runtimes alongside your agent and model spans.