[Solved] In a Kubernetes cluster, if Fluentd is configured to send logs to Elasticsearch at <match **> @type elasticsearch host elasticsearch port 9200 </match> but the Elasticsearch pod crashes, what will... | Kubernetes

Kubernetes - Monitoring and Logging

In a Kubernetes cluster, if Fluentd is configured to send logs to Elasticsearch at

<match **>
  @type elasticsearch
  host elasticsearch
  port 9200
</match>

but the Elasticsearch pod crashes, what will Fluentd do with the incoming logs?

ASend logs to Kibana directly as a fallback

BDiscard the logs immediately without retrying

CBuffer the logs locally and retry sending until Elasticsearch is available

DSwitch to sending logs to a different Elasticsearch cluster automatically

Step-by-Step Solution

Solution:

Step 1: Understand Fluentd buffering
Fluentd buffers logs locally when the output destination is unavailable.
Step 2: Behavior on Elasticsearch downtime
When Elasticsearch is down, Fluentd retries sending logs from its buffer until the service is back.
Final Answer:
Buffer the logs locally and retry sending until Elasticsearch is available -> Option C
Quick Check:
Fluentd uses buffering and retry mechanisms [OK]

Quick Trick: Fluentd buffers logs if Elasticsearch is down [OK]

Common Mistakes:

Master "Monitoring and Logging" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

In a Kubernetes cluster, if Fluentd is configured to send logs to Elasticsearch at