Bitzu

KCNA ยท Observability

Observability and telemetry

Metrics, logs, traces, monitoring vs observability, alerting basics.

Key points

  • Observability is how well you can understand a system's internal state from the data it emits.
  • That data is telemetry: metrics (numeric measurements over time), logs (timestamped event records) and traces (the path of one request across services).
  • Monitoring watches known conditions and alerts on them; observability lets you ask new questions about unknown problems.

Practice questions

Single choice

Which telemetry signal is best suited to following one request as it passes through several microservices?

  1. Metrics
  2. Traces
  3. Event logs
  4. Health probes
Show answer

Answer: B. Traces

A trace links the spans of a single request across services. Metrics aggregate numbers and logs record discrete events, so neither follows one request end to end by themselves.

Select all that apply

Which of these are telemetry signal types?

  1. Metrics
  2. Dashboards
  3. Logs
  4. Runbooks
  5. Traces
Show answer

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

Metrics, logs and traces are the classic signals. Dashboards present data and playbooks are procedures; neither is emitted by a system.

True or false

True or false: monitoring and observability mean exactly the same thing.

Show answer

Answer: False

False. Monitoring checks predefined conditions; observability is the property that lets you investigate unforeseen problems from the data a system emits. Monitoring is one use of that data.

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