Trace Explorer

Correlate request traces across all ExactAgentic API routes

How Trace IDs Work

Every API request generates a UUID v4 trace ID. This ID is:

  • Attached to every pino log entry as traceId
  • Forwarded to EKIS API calls via x-trace-id header
  • Included in circuit breaker state change logs
  • Attached to write verification failure logs

To find a trace ID: check browser DevTools Network tab for the x-trace-id response header, or search CloudWatch logs for any known field (e.g. compositionId, dealershipId).

Log Entry Structure

{
  "level": "info",
  "time": 1711382400000,
  "service": "exactcar-ai",
  "traceId": "550e8400-e29b-41d4-a716-446655440000",
  "route": "/api/admin/orchestrations/execute",
  "dependency": "ekis-api",
  "url": "https://ekus.ai/api/...",
  "status": 200,
  "durationMs": 142,
  "attempt": 1,
  "msg": "fetch succeeded"
}