Container Apps - Replica Memory consumption metrics

Question

Container Apps - Replica Memory consumption metrics

RajivBansal-2486 331

Hi,

I have some container apps. The figures for memory consumption show in Metrics->"Memory Working Set Bytes" with aggregation max is lower than memory consumption show in "Diagnose and Solve Problems"->Container App Memory Usage. Memory allocated to container app is 0.5 GiB per replica.

Metrics->"Memory Working Set Bytes" with aggregation max: shows 465 MBs
Diagnose and Solve Problems"->Container App Memory Usage: shows 515 MBs

Which figure is correct one and why is there difference?

Secondly, Diagnose and Solve Problems section shows that "Container App Out of Memory has been detected". Container was restarted multiple times due to out of memory. But I can't find this information from container app diagnostic logs. Is there any place where I can see details about the out of memory logs.

Thanks,

Rajiv

MayankBargali-MSFT 70,936 Reputation points Moderator

2024-05-27T05:48:24.24+00:00

@Rajiv Bansal Thanks for reaching out.

The "Memory Working Set Bytes" metric shows the maximum amount of memory used by the container instance during the specified time range. On the other hand, "Container App Memory Usage" shows the current memory usage of the container instance. Therefore, the "Memory Working Set Bytes" metric with aggregation max is not a good indicator of the actual memory usage of the container instance.

The "Container App Memory Usage" metric is a better indicator of the actual memory usage of the container instance. Therefore, the figure of 515 MBs is more accurate than 465 MBs.

Regarding your second issue can you please validate the system log and I think ContainerAppSystemlogs_CL table should have those information to troubleshoot the issue.

As Container OOM issue causes app restart events then you can also review the Resource Health section of the Azure portal in case if you find any information on these OOM exceptions.
RajivBansal-2486 331 Reputation points

2024-05-27T07:45:52.8733333+00:00

Hi Mayank,

Thanks for response. Both "Memory Working Set Bytes" metric and "Container App Memory Usage" shows memory usage for given time period. I didn't understood what you meant by "current memory usage".

I already checked ContainerAppsSystemlogs_CL table and didn't found any information regarding container restarts or failure due to any reason.

Thanks!
MayankBargali-MSFT 70,936 Reputation points Moderator

2024-05-29T03:36:21.3833333+00:00

@Rajiv Bansal The Memory Working Set Bytes and Container App Memory Usage is the same but how it is calculated would be different in both places. So, what I mean from monitoring blade Memory Working Set Bytes the difference could be of sample interval, the aggregation over time, etc. could affect what you see with the diagnosis and solve problem blade. If you change the interval. Have you looked into the Resource Health section, and did you see any error exception as you already confirmed that you don't see the logs on ContainerAppsSystemlogs_CL table.

I will suggest us to engage us over one on one support request so we can review the logs to assist you further.

Your answer

MayankBargali-MSFT 70,936 Reputation points Moderator

2024-05-27T05:48:24.24+00:00

@Rajiv Bansal Thanks for reaching out.

The "Memory Working Set Bytes" metric shows the maximum amount of memory used by the container instance during the specified time range. On the other hand, "Container App Memory Usage" shows the current memory usage of the container instance. Therefore, the "Memory Working Set Bytes" metric with aggregation max is not a good indicator of the actual memory usage of the container instance.

The "Container App Memory Usage" metric is a better indicator of the actual memory usage of the container instance. Therefore, the figure of 515 MBs is more accurate than 465 MBs.

Regarding your second issue can you please validate the system log and I think ContainerAppSystemlogs_CL table should have those information to troubleshoot the issue.

As Container OOM issue causes app restart events then you can also review the Resource Health section of the Azure portal in case if you find any information on these OOM exceptions.
RajivBansal-2486 331 Reputation points

2024-05-27T07:45:52.8733333+00:00

Hi Mayank,

Thanks for response. Both "Memory Working Set Bytes" metric and "Container App Memory Usage" shows memory usage for given time period. I didn't understood what you meant by "current memory usage".

I already checked ContainerAppsSystemlogs_CL table and didn't found any information regarding container restarts or failure due to any reason.

Thanks!
MayankBargali-MSFT 70,936 Reputation points Moderator

2024-05-29T03:36:21.3833333+00:00

@Rajiv Bansal The Memory Working Set Bytes and Container App Memory Usage is the same but how it is calculated would be different in both places. So, what I mean from monitoring blade Memory Working Set Bytes the difference could be of sample interval, the aggregation over time, etc. could affect what you see with the diagnosis and solve problem blade. If you change the interval. Have you looked into the Resource Health section, and did you see any error exception as you already confirmed that you don't see the logs on ContainerAppsSystemlogs_CL table.

I will suggest us to engage us over one on one support request so we can review the logs to assist you further.

Share via

Container Apps - Replica Memory consumption metrics

Your answer