With the java code deployed by AKS, if Container Insight is enabled, can we locate the specific java process or thread id that causes OOM? If so, how?

Gallatin 21V 141 Reputation points
2024-03-18T04:57:34.4266667+00:00

https://docs.azure.cn/en-us/azure-monitor/containers/container-insights-logs-schema

Since there is no information about OOM in the documentation, I would like to ask if AKS enables container insight, can it locate the java process and thread id that caused OOM?

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,846 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anveshreddy Nimmala 2,150 Reputation points Microsoft Vendor
    2024-03-19T06:31:22.6666667+00:00

    Hello Gallatin 21V,

    Welcome to microsoft Q&A,Thankyou for posting your query here.

    AKS and Container insights provide a robust infrastructure for monitoring and diagnostics.

    To figure out which part of your Java code caused an "out of memory" error, it might be best to use a mix of tools and methods from both Java and Azure Kubernetes services.

    This way, you can get a clearer picture of what went wrong.

    AKS supports Kubernetes native logging mechanisms that can capture stdout and stderr outputs from containers.

    You can use Container Insights to query these logs and troubleshoot issues with your Java applications, If your Java application logs OOM errors or stack traces to these streams, you can have their output captured and queried through Container insights.

    Hope this helps you,

    If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

    0b4508e5-88d4-45d9-af45-6b9d1a7f7cd0

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful