Tracing

Spans

Each span is one observed operation. Fields come from OTLP attributes and resource metadata you send — defaults are not invented for missing dimensions.

Stored fields

trace_id, span_id, parent_span_id
service, name / operation, status, timing
environment, release
session_id, request / correlation_id when present
Optional attributes JSON as sent (after sanitization)

Hierarchy

Waterfalls use parent_span_id within a trace_id. Orphan spans (missing parent) still appear; Mydle does not invent the parent.

Limitations

Incomplete trees mean incomplete ingest — not a broken renderer inventing children.
Span → logs joins require matching stored span_id on log rows.

Tracing

Spans

Each span is one observed operation. Fields come from OTLP attributes and resource metadata you send — defaults are not invented for missing dimensions.

Stored fields

trace_id, span_id, parent_span_id
service, name / operation, status, timing
environment, release
session_id, request / correlation_id when present
Optional attributes JSON as sent (after sanitization)

Hierarchy

Waterfalls use parent_span_id within a trace_id. Orphan spans (missing parent) still appear; Mydle does not invent the parent.

Limitations

Incomplete trees mean incomplete ingest — not a broken renderer inventing children.
Span → logs joins require matching stored span_id on log rows.

Spans

Stored fields

Hierarchy

Related

Spans

Stored fields

Hierarchy

Related