Bird
0
0

You notice that your Kubernetes logging agent is not forwarding logs to the central system. Which of the following is the most likely cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Monitoring and Logging
You notice that your Kubernetes logging agent is not forwarding logs to the central system. Which of the following is the most likely cause?
AContainers are writing logs to stdout/stderr
BThe logging agent cannot access the /var/log/containers directory on the node
CThe central logging system is storing logs on the node
DKubernetes does not support logging agents
Step-by-Step Solution
Solution:
  1. Step 1: Analyze logging agent failure

    If the agent cannot access the node's log directory, it cannot read logs to forward them.
  2. Step 2: Check other options for correctness

    Containers writing to stdout/stderr is normal; Kubernetes supports logging agents; central system storing logs on node is unrelated to forwarding failure.
  3. Final Answer:

    The logging agent cannot access the /var/log/containers directory on the node -> Option B
  4. Quick Check:

    Agent access to logs = critical [OK]
Quick Trick: Check logging agent's access to node log files first [OK]
Common Mistakes:
  • Blaming containers writing to stdout/stderr
  • Assuming Kubernetes lacks logging agent support
  • Confusing central system storage with forwarding issues

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes