telemetry signal
One of the three main kinds of telemetry: metrics, logs or traces.
In more detail
Each signal answers a different question: metrics say how much or how often, logs say exactly what happened in one event, and traces say where the time went across services for one request. None replaces another. They become one system when they share identifiers such as the service name and the trace ID.
Example
Metrics notice, traces locate, logs explain.Related terms
- metric — A number measured over time, such as requests per second or error count, that shows how a system behaves in aggregate.
- log — A time-stamped record of an individual event in a system, such as one request being handled; structured logs record it as named fields rather than free text.
- trace — A record of one request’s whole journey through a system, made of nested spans that show where the time went.
- correlation — Linking evidence from different signals about the same event, for example from a metric spike to a trace to its log lines.
Taught in
- The Three Signals: Logs, Metrics And Traces — Full-Stack Observability: Metrics, Tracing & Logging
- Cardinality And How It Bankrupts You — Full-Stack Observability: Metrics, Tracing & Logging
- OpenTelemetry: The Vendor Neutral Path — Full-Stack Observability: Metrics, Tracing & Logging
- Instrumenting A Service With Client Libraries — Full-Stack Observability: Metrics, Tracing & Logging
- Bringing The Three Signals Together — Full-Stack Observability: Metrics, Tracing & Logging
- A Worked Example Postmortem — Full-Stack Observability: Metrics, Tracing & Logging