Home › OpenTelemetry (Observability)
OpenTelemetry defines three stable signals (plus profiles, still evolving) that share context and resource information. Signal Answers Building blocks Traces Where did time go in this request across services? trace → spans (name, start/end, attributes, events, status, parent) Metrics How much / how often overall? counters, up-down counters, histograms, gauges + attributes Logs What exactly happened? records with severity, body, attributes, trace/span IDs Key vocabulary Term Meaning Span kind SERVER, CLIENT, PRODUCER, CONSUMER, INTERNAL Attributes key/value details: http.request.method, db.system.name, order.id Events timestamped annotations on a span (e.g. an exception) Resource who emitted it: service.name, service.version, host, k8s pod Semantic conventions standard attribute names so…