Skip to main content

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. 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.
Install the skill once in your coding-agent environment:
Run the framework-specific prompt below from the application root. Review the resulting diff before deploying it.

Manual setup: Agnost AI SDK

Manual setup: OpenTelemetry

VoltAgent ships its own observability layer. Plug an OTLP exporter into VoltAgentObservability, then pass userId / conversationId per call.

1. Install

Already have @voltagent/core and @opentelemetry/exporter-trace-otlp-proto? Skip. No setup yet?

2. Wire the OTel exporter pointing at Agnost AI

Already have VoltAgentObservability? Append a span processor for Agnost AI to the existing spanProcessors array:
No Observability yet? Full setup:

3. Pass userId / conversationId per call

VoltAgent maps userIduser.id and conversationIdconversation.id on every span: both read directly by Agnost AI for user / session grouping.

What appears in Agnost AI

  • Conversations grouped by conversationId.
  • User-level analytics grouped by userId.
  • Events for every exported span.

Verify

Run one agent.generateText call, then open Events and confirm the span arrived.

Troubleshooting

  • Confirm your BatchSpanProcessor is attached to VoltAgentObservability.
  • Confirm X-Agnost-Org-ID is set on the exporter.
  • Confirm userId and conversationId are passed per call.

References

Next steps

  • Conversations: review the complete VoltAgent interaction.
  • Events: inspect agent, model, and tool activity.
  • Intents: organize production conversations by what users wanted.