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
session_id and user_id as Agent constructor params. Spans carry OpenInference attributes plus agno.agent.name / agno.team.name. Instrument once at process start; child agents in teams inherit.
Alternative: OpenLit
openlit.init(...) is also supported and auto-instruments common providers in one shot.
Verify
Run oneagent.print_response call, then open Events in Agnost AI. Confirm spans include session_id, user_id, and agno.agent.name.
Troubleshooting
- Instrument once at process start before agent calls.
- Confirm
OTEL_EXPORTER_OTLP_HEADERScontainsX-Agnost-Org-ID=<your-org-id>. - If child team spans are missing, confirm the parent Agno agent is instrumented before teams are constructed.
References
Next steps
- Conversations: review the complete Agno interaction.
- Events: inspect the spans Agnost AI received.
- Intents: organize production conversations by what users wanted.
