liveBook · Manning

Child span

As explained in Logs and Telemetry

A span is a trace record representing the start and end of a significant operation, optionally nested within another span.

A child span records the start and end of a significant activity nested inside another span. Nesting lets a trace represent an operation composed of smaller services or transactions as a hierarchy rather than a single undifferentiated event. section 3.6.7

Use child spans to preserve the composition of end-to-end work when a transaction crosses services or contains nested activities. The resulting trace can associate those activities with the same transaction context and its metadata. section 3.6.7

Within OpenTelemetry observability data:

  • Logs capture traditional application logging. section 3.6.7
  • Traces organize significant activities as spans, including nested spans. section 3.6.7
  • Metrics measure resource or business values such as CPU use or transactions per minute. section 3.6.7

How Logs and Telemetry covers it

How deep it goes
Defines spans as start-and-end activity records and explains their nesting as a hierarchy.
Examples
Uses services and nested transactions as examples of activities represented by spans.
What you can do after
Evaluate/understand how nested spans model composed transaction activity.
How it connects
Connects child spans with traces, logs, metrics, services, transactions, and baggage.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Logs and Telemetry. The section links point to the parts of the book it draws on.