Signals

Learn about the categories of telemetry supported by OpenTelemetry

The purpose of OpenTelemetry is to collect, process, and export signals. Signals are system outputs that describe the underlying activity of the operating system and applications running on a platform. A signal can be something you want to measure at a specific point in time, like temperature or memory usage, or an event that goes through the components of your distributed system that you’d like to trace. You can group different signals together to observe the inner workings of the same piece of technology under different angles.

OpenTelemetry currently supports traces, metrics, logs and baggage. Events are a specific type of log, and profiles are being worked on by the Profiling Working Group.


Traces

The path of a request through your application.

Metrics

A measurement captured at runtime.

Logs

A recording of an event.

Baggage

Contextual information that is passed between signals.


Last modified December 15, 2023: typo fix for signals page (#3689) (08e13eb6)