v4

latestOpenAPI 3.0.32026-08-0161180264.4 KB

monitoring

integrations

getMonitoringTraceByCorrelation

Returns the cross-system event trace for a correlation_id: every monitoring span sharing it — external spans (middleware) plus epilot's own processing spans — ordered chronologically, with a rolled-up status and the epilot inbound event "head" attached. This is the correlation-grouped counterpart to …/events/{eventId}/associated (which groups a single epilot event's fan-out by event_id). Origin is distinguished by the EXTERNAL_* code prefix on external spans. Freshness is near-real-time (spans land as they are produced/ingested).

get/v2/integrations/{integrationId}/monitoring/traces/{correlationId}

Path parameters

integrationIdstring uuid required

The integration ID

correlationIdstring required

The trace id (correlation_id) shared across systems

Response

The assembled cross-system trace.

correlation_idstring required

The trace id these spans share.

status'success' | 'error' | 'warning' | 'info' required

Rolled-up status across all spans (error > warning > success > info).

started_atstring date-time nullable

created_at of the earliest span (null when the trace is empty).

ended_atstring date-time nullable

created_at of the latest returned span (null when the trace is empty).

span_countinteger required

Number of spans RETURNED (== spans.length; capped).

truncatedboolean required

True when the trace has more spans than the cap; the returned window is the earliest spans, so ended_at/status reflect only that window.

inbound_eventobject nullable

The epilot inbound event "head" (raw payload), when present.