Bird
Raised Fist0

You want to monitor Elasticsearch nodes for CPU and memory usage continuously. Which approach is best?

hard📝 Best Practice Q15 of Q15
Elasticsearch - ELK Stack Integration
You want to monitor Elasticsearch nodes for CPU and memory usage continuously. Which approach is best?
ARestart nodes frequently to reset CPU and memory usage
BUse <code>GET /_cluster/health</code> to check CPU and memory
CInstall Kibana and create dashboards without data collection
DRun <code>GET /_nodes/stats</code> regularly and parse CPU/memory fields
Step-by-Step Solution
Solution:

  1. Step 1: Identify API for node resource stats

    The /_nodes/stats API provides detailed CPU and memory usage per node.

  2. Step 2: Understand monitoring approach

    Regularly running this API and parsing results allows continuous monitoring of resource usage.

  3. Final Answer:

    Run GET /_nodes/stats regularly and parse CPU/memory fields -> Option D

  4. Quick Check:

    Node stats API for CPU/memory monitoring [OK]
Quick Trick: Use /_nodes/stats API for detailed resource monitoring [OK]
Common Mistakes:
MISTAKES
  • Using cluster health API which lacks CPU/memory details
  • Assuming Kibana dashboards work without data
  • Restarting nodes does not monitor usage

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Elasticsearch Quizzes
Advanced Patterns - Search after for efficient pagination - Quiz 3easy Advanced Patterns - Async search for expensive queries - Quiz 13medium Advanced Patterns - Point-in-time API - Quiz 7medium Advanced Patterns - Point-in-time API - Quiz 4medium ELK Stack Integration - Alerting and notifications - Quiz 3easy Performance and Scaling - Replica management - Quiz 10hard Security - Field and document level security - Quiz 13medium Security - Audit logging - Quiz 14medium Security - Why security protects sensitive data - Quiz 15hard Security - API key management - Quiz 12easy