Which of the following is not one of the three pillars of observability?

Which of the following is not one of the three pillars of observability?

• A. Metrics
• B. Logs
• C. Alerts
• D. Traces

Answer: (C)

Observability rests on three pillars: metrics, logs, and traces. Metrics provide numerical measurements over time, like latency, throughput, and error rate. Logs capture discrete events with context, giving details about what happened at a moment. Traces show the path of a single request across services, revealing how components interact and where delays occur. Alerts, while essential for operational response, are not one of the pillars themselves—they’re a notification mechanism that uses the data from those pillars to tell you when something looks off. So the element that isn’t a pillar is alerts.

Observability rests on three pillars: metrics, logs, and traces. Metrics provide numerical measurements over time, like latency, throughput, and error rate. Logs capture discrete events with context, giving details about what happened at a moment. Traces show the path of a single request across services, revealing how components interact and where delays occur. Alerts, while essential for operational response, are not one of the pillars themselves—they’re a notification mechanism that uses the data from those pillars to tell you when something looks off. So the element that isn’t a pillar is alerts.