0

Our container creates log files in /var/appname/app1/java log and other multiple log files. While development,we used to connect the container directly and access the log file using bind mounts. Can anyone suggest how to deal with in azure kubernetes aks? The logs section in monitoring shows only default logs.

I can access the logs using kubectl command or with volumes. But we need this to be visible in azure kubernetes portal logs section so that we can see the daily statistics.

Can you please suggest how to do that.?

azure logs

uday
  • 352
  • 10
  • 30

1 Answers1

0

The official documentation has several recommendations regarding Debug Running Pods:

  • Examining pod logs: by executing kubectl logs ${POD_NAME} ${CONTAINER_NAME} or kubectl logs --previous ${POD_NAME} ${CONTAINER_NAME} if your container has previously crashed

  • Debugging with container exec: run commands inside a specific container with kubectl exec: kubectl exec ${POD_NAME} -c ${CONTAINER_NAME} -- ${CMD} ${ARG1} ${ARG2} ... ${ARGN}

  • Debugging with an ephemeral debug container: Ephemeral containers are useful for interactive troubleshooting when kubectl exec is insufficient because a container has crashed or a container image doesn't include debugging utilities. You can find an example here.

  • Debugging via a shell on the node: If none of these approaches work, you can find the host machine that the pod is running on and SSH into that host.

AKS also helps with that by offering the Container Insights:

Container insights gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers that are available in Kubernetes through the Metrics API. Container logs are also collected.

More sources can be found below:

Wytrzymały Wiktor
  • 806
  • 4
  • 10
  • Many thanks for the links, but my question is how to get custom logs of my application in container insights or monitoring section of aks. – uday Jun 25 '21 at 15:27