What are the three pillars of observability and their deployment relevance?

What are the three pillars of observability and their deployment relevance?

• A. Code quality, test coverage, CI speed.
• B. Metrics, logs, traces; used to verify health, diagnose issues, and understand performance.
• C. Security, compliance, governance.
• D. Availability, scalability, reliability.

Answer: (B)

Observability relies on three kinds of data that together reveal what a system is doing: metrics, logs, and traces. Metrics provide quantitative signals like latency, error rate, and throughput, which you can monitor, trend, and alert on to verify health and performance, especially after deployments. Logs offer detailed, time-stamped records of events and messages from the system, giving the context needed to diagnose issues and understand exactly what happened during an incident. Traces show the path of a single request as it moves through multiple services, exposing where time is spent and how components depend on each other, which helps identify bottlenecks and root causes in distributed environments. In deployment terms, metrics let you quickly spot regressions and confirm that targets are being met; logs supply the investigative breadcrumbs to understand failures or unexpected behavior; traces help you pinpoint where latency or errors propagate across services, making it easier to optimize performance and reliability after changes. Other options describe general software quality or governance concerns, not the specific data types that form the foundation of observability signals.

Observability relies on three kinds of data that together reveal what a system is doing: metrics, logs, and traces. Metrics provide quantitative signals like latency, error rate, and throughput, which you can monitor, trend, and alert on to verify health and performance, especially after deployments. Logs offer detailed, time-stamped records of events and messages from the system, giving the context needed to diagnose issues and understand exactly what happened during an incident. Traces show the path of a single request as it moves through multiple services, exposing where time is spent and how components depend on each other, which helps identify bottlenecks and root causes in distributed environments.

In deployment terms, metrics let you quickly spot regressions and confirm that targets are being met; logs supply the investigative breadcrumbs to understand failures or unexpected behavior; traces help you pinpoint where latency or errors propagate across services, making it easier to optimize performance and reliability after changes.

Other options describe general software quality or governance concerns, not the specific data types that form the foundation of observability signals.