Bird
0
0

Why is it important to use Beats (like Filebeat) instead of sending logs directly from microservices to Elasticsearch?

hard📝 Conceptual Q10 of 15
Microservices - Monitoring and Observability
Why is it important to use Beats (like Filebeat) instead of sending logs directly from microservices to Elasticsearch?
ABeats store logs permanently before sending
BBeats visualize logs in dashboards
CBeats replace Logstash for log parsing
DBeats efficiently ship logs with buffering, retries, and lightweight resource use
Step-by-Step Solution
Solution:

  1. Step 1: Understand Beats role

    Beats are lightweight agents that ship logs reliably with buffering and retries.

  2. Step 2: Check other options

    Beats do not store logs permanently, do not replace Logstash parsing, and do not visualize logs.

  3. Final Answer:

    Beats efficiently ship logs with buffering, retries, and lightweight resource use -> Option D

  4. Quick Check:

    Beats = efficient log shipping agents [OK]
Quick Trick: Use Beats for reliable, lightweight log shipping [OK]
Common Mistakes:
MISTAKES
  • Thinking Beats store logs permanently
  • Confusing Beats with Logstash parsing
  • Assuming Beats visualize logs

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 7medium Event-Driven Architecture - Event schema design - Quiz 6medium Monitoring and Observability - Distributed tracing (Jaeger, Zipkin) - Quiz 12easy Orchestration with Kubernetes - Liveness and readiness probes - Quiz 2easy Resilience Patterns - Graceful degradation - Quiz 2easy Resilience Patterns - Circuit breaker pattern - Quiz 12easy Resilience Patterns - Retry with exponential backoff - Quiz 9hard Service Mesh - Mutual TLS between services - Quiz 7medium Service Mesh - Service mesh concept - Quiz 11easy Service Mesh - Traffic management (routing, splitting) - Quiz 14medium