Events

An event is one captured operation inside a conversation. Depending on the instrumentation, it may represent an agent turn, model generation, tool call, handoff, guardrail, or another traced operation.

Inspect events

Open Events in the Voxmith sidebar to review the unaggregated telemetry stream. Use it first when verifying a new setup: an event can arrive before higher-level classification and aggregation finishes.

Confirm that a test event contains:

• The expected workspace and conversation identifier.
• A stable user identifier.
• The correct agent, model, framework, or operation name.
• The expected input and output.
• Success state, latency, timestamp, and useful metadata.

Events and conversations

Conversation
├── Agent turn event
├── Tool call event
└── Agent turn event

The ingestion API calls the conversation boundary a session. Create the session once, then send its events with the same session_id. See Capture Session and Capture Event.

Troubleshooting

• Missing event: verify the endpoint, organization ID, and org header.
• Fragmented conversation: reuse the same conversation/session identifier.
• Missing text: check framework content-capture settings.
• Duplicate operation: avoid enabling two instrumentation paths around the same call unless you intentionally want both records.

Next steps

• Conversations: see how related events become one interaction.
• Tool calls: analyze tool-specific execution details.
• Ingestion errors: troubleshoot events that do not arrive as expected.