Bird
0
0

You deployed the EFK stack but Kibana shows no logs. Which of these is the most likely cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Monitoring and Logging
You deployed the EFK stack but Kibana shows no logs. Which of these is the most likely cause?
AKibana is configured to use wrong Elasticsearch URL
BElasticsearch service port is set to 8080 instead of 9200
CAll of the above
DFluentd DaemonSet is not running on nodes
Step-by-Step Solution
Solution:

  1. Step 1: Check Fluentd status

    If Fluentd pods are not running, logs won't be collected or sent.

  2. Step 2: Verify Elasticsearch connectivity

    Wrong port on Elasticsearch service means Fluentd can't send logs properly.

  3. Step 3: Confirm Kibana configuration

    If Kibana points to wrong Elasticsearch URL, it can't display logs.

  4. Final Answer:

    All of the above -> Option C

  5. Quick Check:

    Any broken link in EFK stops logs [OK]
Quick Trick: Check Fluentd, Elasticsearch port, Kibana URL [OK]
Common Mistakes:
  • Checking only one component
  • Ignoring service port mismatch
  • Assuming Kibana auto-fixes URLs

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Advanced Deployment Patterns - Why advanced patterns matter - Quiz 12easy Advanced Deployment Patterns - Feature flags in Kubernetes - Quiz 13medium Helm Package Manager - Helm charts concept - Quiz 8hard Helm Package Manager - Why Helm simplifies deployments - Quiz 12easy Monitoring and Logging - Why cluster monitoring matters - Quiz 10hard RBAC and Security - Secrets encryption at rest - Quiz 6medium Service Mesh - Mutual TLS for service communication - Quiz 12easy Service Mesh - Traffic management with Istio - Quiz 6medium Service Mesh - Linkerd as lightweight alternative - Quiz 8hard Troubleshooting - Node troubleshooting - Quiz 13medium