Bird
0
0

Why might logs sent to a centralized Fluentd server from Docker containers sometimes be missing or incomplete?

hard📝 Conceptual Q10 of 15
Docker - Logging and Monitoring
Why might logs sent to a centralized Fluentd server from Docker containers sometimes be missing or incomplete?
ANetwork issues or Fluentd buffer overflow causing log loss
BDocker containers do not generate logs by default
CFluentd does not support Docker log format
DDocker logging drivers encrypt logs preventing Fluentd reading
Step-by-Step Solution
Solution:

  1. Step 1: Identify common causes of log loss

    Network problems or Fluentd buffers filling up can cause logs to be lost or delayed.

  2. Step 2: Eliminate incorrect reasons

    Docker containers generate logs by default; Fluentd supports Docker logs; Docker logging drivers do not encrypt logs by default.

  3. Final Answer:

    Network issues or Fluentd buffer overflow causing log loss -> Option A

  4. Quick Check:

    Network and buffer issues cause missing logs in centralized setup [OK]
Quick Trick: Check network and Fluentd buffers if logs are missing [OK]
Common Mistakes:
  • Thinking Docker containers don't log by default
  • Believing Fluentd can't parse Docker logs
  • Assuming logs are encrypted by default

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - Read-only filesystem containers - Quiz 13medium Docker Security - Content trust and image signing - Quiz 13medium Docker Security - User namespace remapping - Quiz 5medium Docker Security - Running containers as non-root - Quiz 15hard Docker Swarm - Why orchestration matters - Quiz 12easy Docker Swarm - Swarm vs Kubernetes decision - Quiz 7medium Logging and Monitoring - Why monitoring containers matters - Quiz 12easy Logging and Monitoring - Docker events monitoring - Quiz 6medium Resource Management - System prune for cleanup - Quiz 6medium Resource Management - System prune for cleanup - Quiz 1easy