Monitor and Output Logs to a File in Kubernetes

30 minutes
  • 3 Learning Objectives

About this Hands-on Lab

You can troubleshoot broken pods quickly using the `kubectl logs` command. You can manipulate the output and save it to a file in order to capture important data. In this hands-on lab, you will be presented with a broken pod, and you must collect the logs and save them to a file in order to better understand the issue.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Identify the problematic pod in your cluster.

Use the following command to view all the pods in your cluster:

kubectl get pods --all-namespaces
Collect the logs from the pod.

Use the following command to collect the logs from the pod:

kubectl logs <pod_name> -n <namespace_name>
Output the logs to a file.

Use the following command to output the logs to a file:

kubectl logs <pod_name> -n <namespace_name> > broken-pod.log

Additional Resources

You have been given access to a three-node cluster. Within that cluster, you must discover the pod that isn’t running as it should. Then, you must collect the logs and save them to a file in order to capture the problematic messages from the log. Perform the following tasks in order to complete this hands-on lab:

  • Identify the pod that is not running in the cluster.
  • Collect the logs from the pod and try to identify the problem.
  • Output the logs to a file in order to share that file with your colleagues.

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?