Choose a setup method
Start with one method for a call path. Combining SDK tracking with framework
OpenTelemetry on the same call can create duplicate interactions.
Recommended: Agnost AI skill
Recommended. Choose this path when you want your coding agent to inspect the
project, select a supported transport, make the smallest instrumentation change,
send a test event, and verify that it reached Agnost AI.
Manual setup: Agnost AI SDK
Manual setup: OpenTelemetry
Install
Setup
dspy.module, dspy.signature, plus standard OpenInference input.value / output.value. Pair with a provider instrumentation (e.g. OpenAIInstrumentor) for the deepest trace tree.
Alternative: MLflow
If you already use MLflow,mlflow.dspy.autolog() works too: Agnost AI reads mlflow.spanInputs / mlflow.spanOutputs.
Verify
Run one DSPy module call, then open Events in Agnost AI. Confirmdspy.module and input/output attributes are present.
Troubleshooting
- Instrument DSPy before calling modules.
- Pair DSPy instrumentation with provider instrumentation if you need LLM-level spans.
- Confirm
OTEL_EXPORTER_OTLP_HEADERScontainsX-Agnost-Org-ID=<your-org-id>.
References
Next steps
- Conversations: review the complete DSPy interaction.
- Events: inspect module and model activity.
- Intents: organize production conversations by what users wanted.
