Questão de System Administration #019e3a4f

The three pillars of observability are Metrics, Logs, and Traces. This is a foundational concept in modern software systems, particularly in cloud-native and microservices architectures.

How it Works

Observability is the ability to understand the internal state of a system by examining its outputs. The three pillars provide different perspectives:

• Metrics are numerical measurements over time (e.g., CPU usage, request latency). They are aggregated and used for alerting and trend analysis.
• Logs are discrete, timestamped records of events (e.g., error messages, access logs). They provide detailed context for debugging.
• Traces represent the path of a request as it travels through distributed services (e.g., spans in a distributed trace). They help identify bottlenecks and failures in complex systems.

Why the Correct Value is Right

The combination of Metrics, Logs, and Traces is widely accepted in the industry (e.g., by the OpenTelemetry project, Google's SRE practices, and CNCF landscape). Each pillar addresses a distinct aspect of system observability, and together they provide comprehensive visibility.

Why the Incorrect Values are Wrong

• Metrics, Logs, and Spans: Spans are a component of traces, not a separate pillar. The correct term is "traces," which encompass spans.
• Metrics, Data, and Traces: "Data" is too generic and not a specific pillar. Observability pillars are precisely defined as metrics, logs, and traces.
• Resources, Logs, and Tracing: "Resources" is not a pillar; it refers to system components like CPU or memory. Tracing is a process, but the pillar is "traces" (the output).