Bitzu

KCNA ยท Observability

Logging, tracing and OpenTelemetry

Node-level logging agents (Fluentd, Fluent Bit), distributed tracing, Jaeger, OpenTelemetry signals and collector.

Key points

  • Containers log to stdout and stderr; the runtime stores logs on the node, the kubelet serves them to kubectl logs.
  • These files vanish with the node or pod, so a node-level agent (Fluentd, Fluent Bit) ships them to a central backend.
  • Jaeger: CNCF graduated distributed tracing system.
  • OpenTelemetry: vendor-neutral standard and toolset (APIs, SDKs, Collector) to generate and export metrics, logs and traces.

Source: https://kubernetes.io/docs/concepts/cluster-administration/logging/

Practice questions

Single choice

What is the main purpose of the OpenTelemetry Collector?

  1. Receive, process and export telemetry data to backends
  2. Schedule pods onto nodes
  3. Store all logs permanently on the control plane
  4. Run containers on each node
Show answer

Answer: A. Receive, process and export telemetry data to backends

The Collector receives, processes and exports telemetry in a vendor-neutral way. It is not a storage database, a scheduler or a container runtime.

Select all that apply

Which of these are signals that OpenTelemetry defines?

  1. Traces
  2. Container images
  3. Metrics
  4. Logs
  5. Network policies
Show answer

Answer: A. Traces, C. Metrics, D. Logs

OpenTelemetry covers traces, metrics and logs. Container images and network policies are unrelated to telemetry signals.

True or false

True or false: OpenTelemetry is a backend that stores and visualizes your traces.

Show answer

Answer: False

False. OpenTelemetry generates, collects and exports telemetry; you send it to a backend such as Jaeger or Prometheus for storage and analysis.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More KCNA topics in this module