Glossary

Short, precise definitions of the observability and OpenTelemetry terms used across Maple's guides and docs, each with an example.

Terms

Trace
A trace is the record of one request or operation as it moves through a system, made of spans that share one trace ID and form a tree of parent and child operations.
Span
A span is one timed operation inside a trace, such as an HTTP request, a database query or a function call, with a name, a start and end time, attributes, events and a status.
OTLP
OTLP, the OpenTelemetry Protocol, is the vendor-neutral format for sending traces, metrics and logs from OpenTelemetry SDKs and Collectors to a backend, over gRPC on port 4317 or HTTP on port 4318.
Percentiles (p50, p95, p99)
A percentile is the value below which a given share of measurements fall: p99 latency is the response time that 99% of requests beat and the slowest 1% exceed.
SLO and error budget
A service level objective (SLO) is a target for how often a service must behave well over a time window, such as 99.9% of requests succeeding over 30 days. The error budget is the failure that target allows: 0.1% of requests.
Cardinality
In observability, cardinality is the number of distinct values an attribute takes, and for a metric the number of distinct time series its attribute combinations produce.
Instrumentation and auto-instrumentation
Instrumentation is the code that produces telemetry from an application. Auto-instrumentation adds it without changes to your code, by patching common libraries at startup; manual instrumentation is spans and metrics you write yourself.
Semantic conventions
OpenTelemetry semantic conventions are the standard names and values for telemetry attributes, metrics and spans, such as http.request.method or service.name, so data from any library or language means the same thing.

Go deeper: OpenTelemetry in production

  1. Part 1 of 5 The OpenTelemetry Collector Receivers, processors and exporters, a config that runs, and when to deploy an agent or a gateway.
  2. Part 2 of 5 OTLP explained gRPC or HTTP, ports 4317 and 4318, protobuf or JSON, auth headers, and the export errors you will hit.
  3. Part 3 of 5 OpenTelemetry sampling Head and tail sampling, parent-based ratios, a tail sampling config, and what sampling does to metrics and cost.
  4. Part 4 of 5 Context propagation and trace IDs in logs How traceparent and baggage cross services, and how to put trace_id and span_id on every log line.
  5. Part 5 of 5 Metric cardinality What a time series is, how one attribute multiplies a bill, and how to find and fix it.

오늘 첫 트레이스를 확인하세요.

SDK를 추가하고 OTLP 익스포터를 Maple로 향하게 하면 트레이스가 도착합니다.

maple.dev: OpenTelemetry 위의 옵저버빌리티