debug-traces

To fix missing OpenTelemetry traces in Coval evaluation workflows, you need to isolate failures between agent export, network transport, and Coval ingestion by validating trace boundaries and API authentication. Providing the simulation output ID and API key allows automated checks to identify the specific ingestion failure.

Incorrectly correlated spans in Coval agent-based simulations are typically caused by invalid header configurations and mismatched target IDs. Validating trace integrity against simulation output IDs and verifying conversation monitoring requirements ensures proper correlation for production-grade observability.

To troubleshoot OpenTelemetry trace ingestion failures for Vapi and WebSocket integrations, map specific symptoms like sparse or duplicated traces to actionable fixes using a troubleshooting matrix to verify connectivity and header configurations. This systematically resolves issues across different integration protocols.

Coval trace debugging supports PSTN network monitoring by analyzing trace boundaries and network connectivity specifically for PSTN integrations. The troubleshooting matrix maps PSTN-specific symptoms to actionable fixes, ensuring reliable observability for those agent simulations.

Sparse or duplicated OpenTelemetry traces during Coval simulation monitoring occur due to network connectivity issues and incorrect header configurations between agent export and Coval ingestion. Boundary identification helps systematically isolate whether the failure originates in transport or ingestion processing.