Bird
0
0

You are designing a microservices system and want to implement the three pillars: metrics, logs, and traces. Which approach best ensures scalability and effective monitoring?

hard📝 Trade-off Q15 of 15
Microservices - Monitoring and Observability
You are designing a microservices system and want to implement the three pillars: metrics, logs, and traces. Which approach best ensures scalability and effective monitoring?
AUse a centralized monitoring system that collects metrics via Prometheus, logs via ELK stack, and traces via OpenTelemetry.
BStore all logs and traces locally on each service to reduce network overhead.
COnly collect metrics and ignore logs and traces to save storage space.
DSend all raw logs and traces directly to the client application for analysis.
Step-by-Step Solution
Solution:

  1. Step 1: Identify best practices for scalable monitoring

    Centralized systems like Prometheus for metrics, ELK for logs, and OpenTelemetry for traces are industry standards for scalability and analysis.

  2. Step 2: Evaluate options for scalability and effectiveness

    Local storage limits analysis and scalability; ignoring logs/traces loses insights; sending raw data to clients is inefficient and insecure.

  3. Final Answer:

    Use a centralized monitoring system that collects metrics via Prometheus, logs via ELK stack, and traces via OpenTelemetry. -> Option A

  4. Quick Check:

    Centralized, specialized tools = scalable monitoring [OK]
Quick Trick: Centralize collection with proven tools for all three pillars [OK]
Common Mistakes:
MISTAKES
  • Storing logs/traces locally only
  • Ignoring logs or traces
  • Sending raw data directly to clients

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Authentication and Authorization - JWT token propagation - Quiz 8hard Authentication and Authorization - API key management - Quiz 15hard Event-Driven Architecture - Idempotent event consumers - Quiz 12easy Event-Driven Architecture - Event store concept - Quiz 15hard Monitoring and Observability - Dashboards (Grafana) - Quiz 5medium Monitoring and Observability - Why observability is critical in distributed systems - Quiz 12easy Monitoring and Observability - Distributed tracing (Jaeger, Zipkin) - Quiz 10hard Orchestration with Kubernetes - Namespace isolation - Quiz 9hard Resilience Patterns - Circuit breaker pattern - Quiz 14medium Resilience Patterns - Timeout pattern - Quiz 4medium