ELK Monitoring Interview Questions for DevOps (2027)

40 ELK monitoring interview questions: Elastic Agent, Fleet, Kibana alerting, SLOs and burn rate, Stack Monitoring, AutoOps and cluster health scenarios.

Sep 17, 2025 - 11:19
Nov 6, 2026 - 15:21
 0  67
ELK Monitoring Interview Questions for DevOps (2027)

ELK monitoring interview questions ask two things: how you use the Elastic Stack to monitor applications and infrastructure (Elastic Agent, Fleet, integrations, alerting rules, SLOs, APM), and how you monitor the Elastic cluster itself (cluster health, Stack Monitoring, AutoOps). Good answers name the signal, the tool that collects it and the alert you would build on it. This page has 40 questions grouped by level, with monitoring scenarios at the end.

The rest of our ELK series covers other angles: 80+ ELK Stack interview questions is the main list, real-time ELK questions focuses on production incidents, and Elastic certification exam prep covers the official exams. This page stays on monitoring and alerting design.

Key takeaways

  • Elastic recommends Elastic Agent, managed from Fleet, for collecting monitoring data from Elasticsearch, Kibana and Logstash. Metricbeat is the alternative; the legacy internal collection methods are not recommended.
  • Ship monitoring data to a separate monitoring cluster in production. Elastic notes a monitoring cluster cannot monitor production clusters running newer stack versions.
  • AutoOps is Elastic's alternative to Stack Monitoring for issue detection with suggested fixes, available for Elastic Cloud Hosted, Serverless, ECE, ECK and self-managed clusters.
  • Kibana alerting is built from rules, connectors and actions. Alert summaries reduce notification noise.
  • Elastic Observability SLOs can be built from custom KQL queries and APM latency or availability data, and burn rate rules alert on fast error budget use. SLOs need an appropriate subscription.

What you monitor and with which Elastic feature

SignalCollected byViewed inTypical alert
Application and system logsElastic Agent integrations, Filebeat, LogstashDiscover, Logs viewsError count above a threshold
Host and container metricsElastic Agent (system, Kubernetes integrations), MetricbeatInfrastructure inventory, dashboardsCPU, memory or disk over limit
Traces and service latencyAPM agents or OpenTelemetryAPM / Applications UILatency or error rate rule, SLO burn rate
Uptime and endpointsSynthetics monitorsSynthetics appMonitor down
Elastic cluster healthElastic Agent or Metricbeat to a monitoring cluster, or AutoOpsStack Monitoring, AutoOpsCluster status red, disk watermark, JVM pressure

Freshers: monitoring basics with ELK

1. How does the ELK Stack fit into DevOps monitoring?

Agents collect logs, metrics and traces; Elasticsearch stores and indexes them; Kibana searches, visualises and alerts on them. Logstash is used when you need heavier parsing or routing. Together they give one place to investigate incidents. See the role of ELK in centralized logging.

2. Logs, metrics and traces: what is the difference?

Logs are timestamped event records. Metrics are numeric measurements over time, such as CPU percent. Traces follow one request across services and show where time was spent. Each answers a different question during an incident.

3. What is Elastic Agent?

A single agent that collects logs, metrics and other data using integrations, and can also provide security protections. It replaces running several separate Beats on each host.

4. What is Fleet?

The Kibana app that manages Elastic Agents centrally. You define agent policies with integrations, and enrolled agents receive updates automatically. Fleet Server handles agent communication.

5. What is an integration?

A package that adds a data source to an agent policy, for example System, NGINX, PostgreSQL or Kubernetes. It usually brings ingest pipelines, mappings and ready-made dashboards with it.

6. Filebeat vs Logstash: when do you use each?

Filebeat is a light shipper on each host that reads files and sends events. Logstash runs centrally and handles complex parsing, enrichment and routing to multiple outputs. Many setups use agents to ship and ingest pipelines to parse, adding Logstash only when needed.

7. What does cluster health green, yellow and red mean?

Green: all primary and replica shards are assigned. Yellow: all primaries are assigned but some replicas are not. Red: at least one primary shard is unassigned, so some data is unavailable for search or indexing.

8. Which APIs give a quick view of cluster state?

GET _cluster/health for overall status, GET _cat/nodes?v for node load and heap, GET _cat/indices?v for index size and health, and GET _cat/shards?v for shard placement.

curl -s -u "$ES_USER:$ES_PASS" "https://es.example.internal:9200/_cluster/health?pretty"
curl -s -u "$ES_USER:$ES_PASS" "https://es.example.internal:9200/_cat/nodes?v&h=name,heap.percent,cpu,load_1m,node.role"

9. What is a Kibana dashboard used for in monitoring?

It groups visualisations, such as error rate, latency and resource use, on one screen so on-call engineers can see the state of a service quickly. Integrations ship prebuilt dashboards you can copy and customise.

10. What is the Elastic Common Schema and why does it help monitoring?

ECS gives standard field names like host.name, service.name and log.level. When all sources follow it, one query or dashboard works across services and correlation is easier.

11. What is index lifecycle management in a monitoring setup?

ILM rolls over log and metric indices and deletes or moves them to cheaper tiers by age. Without it, monitoring data grows until the disks fill.

12. What is a data stream?

The standard target for time-series data like logs and metrics. You write to one name, and Elasticsearch manages hidden backing indices that roll over with ILM.

2-5 years: alerting, SLOs and stack monitoring

13. How is alerting structured in Kibana?

A rule checks data on a schedule against conditions. When conditions are met, the rule creates alerts and runs actions, which use connectors such as email, Slack, PagerDuty or a webhook to send notifications. Recovery actions can run when the condition clears.

14. What is the Elasticsearch query rule type?

A rule that runs a query (KQL, Query DSL or ES|QL) against indices on a schedule and alerts when the number of matches crosses a threshold. It suits checks like "more than 50 errors from checkout in 5 minutes".

15. What are alert summaries?

For rule types that support them, Kibana can group new, ongoing and recovered alerts into one summary sent on an interval. It cuts notification volume compared with one message per alert.

16. How do you avoid noisy alerts?

Alert on user-facing symptoms such as error rate and latency, not every CPU spike. Use time windows long enough to ignore blips, use alert summaries, route alerts to the owning team and review alerts nobody acted on.

17. What is an SLO in Elastic Observability?

A service level objective defined on an SLI, such as the share of requests under a latency target. Elastic computes the SLI from custom KQL queries or APM latency and availability data and shows the remaining error budget.

18. What is burn rate?

How fast you are using the error budget compared with the allowed pace. Elastic's SLO view shows burn rate across 1-hour, 6-hour, 24-hour and 72-hour windows. Burn rate rules alert when the budget is being spent too fast.

19. What does Stack Monitoring show?

Health and performance of Elasticsearch, Kibana and Logstash: cluster status, node CPU and JVM heap, indexing and search rates, shard counts and Logstash pipeline throughput.

20. Which collection method does Elastic recommend for Stack Monitoring?

Elastic Agent, managed through Fleet. Metricbeat is supported for teams already using Beats. The legacy collection methods, which use internal exporters, are not recommended.

21. Why use a separate monitoring cluster?

If the production cluster is in trouble, its own monitoring data may be missing exactly when you need it. A separate cluster keeps monitoring available and keeps that load off production. Keep its version the same or newer than the clusters it monitors.

22. What is AutoOps?

An Elastic service that analyses cluster metrics, detects issues and suggests resolution steps. Elastic offers it for Elastic Cloud Hosted, Serverless, ECE, ECK and self-managed deployments as an alternative to Stack Monitoring.

23. Which Elasticsearch metrics deserve alerts?

Cluster status red, nodes leaving the cluster, disk usage approaching the high watermark, sustained JVM heap pressure, rejected thread pool tasks for write or search, and a rising count of unassigned shards.

24. What are disk watermarks?

Thresholds that control shard allocation by disk use. Past the low watermark, Elasticsearch stops allocating new shards to the node; past the high watermark, it moves shards away; at the flood stage, it blocks writes to affected indices. Check the defaults for your version in the docs.

25. How do you monitor Logstash?

Collect its metrics through Stack Monitoring or call the node stats API on its monitoring port to see events in and out, filter duration and queue size per pipeline. A growing persistent queue means outputs cannot keep up.

26. How do you monitor Kubernetes with Elastic?

Run Elastic Agent as a DaemonSet with the Kubernetes integration to collect node, pod and container metrics and container logs, plus cluster-level data from kube-state-metrics. Dashboards then show resource use per namespace and workload.

27. What is APM in Elastic?

Application performance monitoring. APM agents or OpenTelemetry SDKs send traces, spans and errors, and the UI shows service maps, latency distributions and slow transactions.

28. Can Elastic accept OpenTelemetry data?

Yes. Elastic supports ingesting OpenTelemetry traces, metrics and logs, so teams can instrument with OpenTelemetry and still analyse in Elastic. Check the Elastic docs for the supported collector setup for your version.

29. What is Synthetics monitoring?

Scheduled checks from outside the application, such as HTTP, TCP or browser journeys, that confirm endpoints are up and flows work. They catch outages even when no user traffic arrives.

30. How do you correlate a latency spike with logs?

Start from the APM transaction or trace with high latency, follow its trace ID to the logs of the services involved, and look for errors or slow queries in the same time window. Shared fields like trace.id and service.name make this possible.

Senior: monitoring design

31. How would you design ELK monitoring for 200 microservices?

Standardise on ECS fields and Elastic Agent policies per environment, send traces through OpenTelemetry or APM agents, define SLOs per user-facing service, alert on burn rate instead of raw thresholds, and use ILM with hot-warm-frozen tiers to control cost.

32. How do you control the cost of monitoring data?

Drop noisy fields and debug logs at ingest, shorten retention on the hot tier, move older data to cheaper tiers or searchable snapshots, and sample traces. Review which data nobody queries.

33. ELK vs Prometheus and Grafana for monitoring: how do you choose?

Prometheus is strong for metrics and Kubernetes-native alerting; Elastic is strong for log search and correlating logs, metrics and traces in one store. Many teams run both. Our Prometheus and Grafana guide covers that side, and top observability tools compares wider options.

34. How do you keep monitoring available during a major incident?

Use a separate monitoring cluster or managed service, alert on the absence of data, give on-call staff access that does not depend on the failing systems, and keep runbooks linked from alerts.

Scenario questions

35. Cluster status turns red at 2 AM. What do you do?

Run GET _cluster/health and GET _cat/shards?v to find the red indices, then GET _cluster/allocation/explain for the reason. Common causes are a lost node or disk at flood stage. Restore the node or free disk; restore from snapshot only if a primary is truly lost.

36. Logs from one service stopped appearing in Kibana. Where do you look?

Check the agent's status in Fleet and its logs on the host, then whether the data stream is still receiving documents, then ingest pipeline errors and mapping conflicts. Also check the Kibana time picker and data view, which cause many false alarms.

37. Alerts fire every few minutes for the same problem. How do you fix the noise?

Switch to alert summaries or a longer action frequency, widen the rule's time window, and make sure recovery actions clear the alert. If the alert is not actionable, remove it.

38. Indexing slows down and write rejections appear. What do you check?

Look at write thread pool rejections and queue size per node, JVM heap and disk I/O, refresh interval and bulk request sizes. Hot shards on one node often cause it; rebalance shards or add hot nodes.

39. Stack Monitoring shows no data for one node. Why?

The agent or Metricbeat on that node may be down, its credentials may have expired, or the node may run a newer version than the monitoring cluster supports. Check the collector's logs and the version match.

40. Management asks for a weekly reliability report. What would you include?

SLO attainment and error budget remaining per service, incidents and their duration, top recurring alerts, and capacity trends for the cluster. Build it as a Kibana dashboard so it updates itself.

How to prepare

  1. Install Elasticsearch and Kibana, enrol one Elastic Agent through Fleet and add the System integration.
  2. Create an Elasticsearch query rule with an email or webhook connector and trigger it on purpose.
  3. Instrument a small app with an APM agent or OpenTelemetry and find a slow request in the traces.
  4. Set up Stack Monitoring to a second cluster and watch node metrics while you load data.
  5. Break things: fill a disk, stop a node, misconfigure a pipeline, and practise the recovery.

For structured labs on Elasticsearch, Logstash, Kibana and monitoring, see the ELK Stack training in Pune or the Prometheus and Grafana training, both in our Kharadi classroom and live online.

FAQ

Is ELK good for DevOps monitoring?

Yes, especially for logs and for correlating logs with metrics and traces. Many teams pair it with Prometheus for Kubernetes metrics.

What is the recommended way to monitor an Elasticsearch cluster?

Elastic recommends Elastic Agent managed by Fleet, sending data to a separate monitoring cluster, or using AutoOps. Metricbeat is an alternative; legacy internal collection is not recommended.

What does a yellow cluster status mean?

All primary shards are assigned but at least one replica is not. Data is available, but you have less redundancy than configured.

How do I set up alerts in Kibana?

Create a rule with conditions and a schedule, attach actions that use a connector such as email, Slack or a webhook, and choose how often actions run or whether to send summaries.

Do Elastic SLOs need a paid licence?

Elastic's SLO documentation says an appropriate subscription is required. Check Elastic's subscriptions page for the current tier.

What is the difference between Stack Monitoring and AutoOps?

Stack Monitoring collects and shows metrics for Elasticsearch, Kibana and Logstash. AutoOps adds automatic issue detection with suggested resolution steps.

Which questions do senior monitoring interviews ask?

Design of collection at scale, SLOs and burn rate alerting, cost control with ILM and tiers, and how monitoring stays available during incidents.

Official references

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.