How does observability differ from monitoring, and how do you implement both?

• A. Monitoring tracks metrics; observability enables explaining behavior via logs/traces/metrics; implement with centralized dashboards, alerts, and tracing.
• B. Observability is the same as monitoring and uses the same tools.
• C. Observability focuses only on network health; monitoring focuses on code quality.
• D. Monitoring collects traces only; observability ignores logs.

Answer: (A)

Observability is about understanding why a system behaves the way it does by collecting and linking multiple signals—metrics, logs, and traces—so you can explain unexpected behavior and diagnose root causes. Monitoring is the ongoing watching of predefined indicators and thresholds to detect issues and raise alerts. The best choice captures this distinction and describes a practical way to implement both: instrument services to emit metrics, logs, and traces; centralize them in a single telemetry backend; build dashboards to visualize current state; set up alerts on key metrics; and use distributed tracing to follow a request across services. Logs provide context, traces show the path of a request through components, and metrics give quantitative signals; together they enable rapid diagnosis and understanding of complex failures. The other options misstate or narrow the concept—treating observability as the same as monitoring, focusing only on networks, or insisting you only collect traces and ignore logs—missing the full breadth needed to explain system behavior.