How can I troubleshoot requests to an Azure Container App? - Stack Overflow

admin管理员组

文章数量:1402976

I have a Container App which I want to scale down when unused. The Container App receives one request every five minutes, meaning that it is never scaled down. I want to find out where the request is coming from.

Sources I have ruled out:

• Application gateway: the Container App is deployed behind an Application gateway, but its health probe is configured to run once every hour to avoid keeping the Container App scaled up.
• Probes on the Container App: there are no probes of any kind configured.

I have checked the following log sources, none have any relevant events at the expected timestamps:

• ContainerAppSystemLogs_CL for the Container App
• ContainerAppConsoleLogs_CL for the Container App
• The Log stream for both Console and System logs
• Logs for the Application gateway

I have managed to figure out where the request came from. It was from an internal service that, due to a recent private DNS zone reconfiguration, hit the Container App from within the virtual network instead of going through the Application Gateway. Thinking of that was mainly luck, and I would still like to know where to find the tools for proper troubleshooting.

I have a Container App which I want to scale down when unused. The Container App receives one request every five minutes, meaning that it is never scaled down. I want to find out where the request is coming from.

Sources I have ruled out:

• Application gateway: the Container App is deployed behind an Application gateway, but its health probe is configured to run once every hour to avoid keeping the Container App scaled up.
• Probes on the Container App: there are no probes of any kind configured.

I have checked the following log sources, none have any relevant events at the expected timestamps:

• ContainerAppSystemLogs_CL for the Container App
• ContainerAppConsoleLogs_CL for the Container App
• The Log stream for both Console and System logs
• Logs for the Application gateway

I have managed to figure out where the request came from. It was from an internal service that, due to a recent private DNS zone reconfiguration, hit the Container App from within the virtual network instead of going through the Application Gateway. Thinking of that was mainly luck, and I would still like to know where to find the tools for proper troubleshooting.

• azure
• azure-container-apps

Share Improve this question Follow edited Mar 28 at 11:13 Vinay B 2,72622 gold badges33 silver badges1212 bronze badges Recognized by Microsoft Azure Collective asked Mar 27 at 13:28 HenricFHenricF 22044 silver badges1919 bronze badges 3

• 1 Try enabling diagnostics in Azure Monitor for your Container App, use Network Security Group (NSG) flow logs and Azure Application Insights Request Telemetry to track internal requests, and analyze Azure Monitor Logs for request origins @HenricF – Vinay B Commented Mar 28 at 3:37
• Thank you, @VinayB. The NSG flow logs look promising. Do you want to add it as an answer, so I can accept it? – HenricF Commented Mar 28 at 10:57
• 1 sure I will share the same as solution so that it would be helpfull for the community @henricF – Vinay B Commented Mar 28 at 11:06

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

Diagnosing Unexpected Requests Keeping an Azure Container App Scaled Up

Continuing from the comments mentioned, glad to know the solution approach shared was works for you.

In order to make a track and diagnose the requests, keeping an Azure container app scaled up while enabled diagnostics in Azure Monitor is an important step. With this, the collections of system logs can be allowed.

Refer: https://learn.microsoft/en-us/azure/azure-monitor/essentials/diagnostic-settings

If the Container app is deployed in a VNET and NSG Flow logs in Azure Network Watcher can help you capture network traffic, Application Insights Request Telemetry gives deeper insights into incoming requests, capturing details such as IP addresses, request paths, and dependencies.

Refer:

https://learn.microsoft/en-us/azure/azure-monitor/app/app-insights-overview

https://learn.microsoft/en-us/azure/network-watcher/nsg-flow-logs-overview

So ContainerAppIngressLogs_CL and ContainerAppSystemLogs_CL in Log Analytics Workspace helps to pinpoint request origins, whether from an internal service, an external probe.

By leveraging a combination of Azure Monitor, Network Watcher, and Application Insights, it becomes possible to systematically track request patterns and optimize scaling behavior.

本文标签： How can I troubleshoot requests to an Azure Container AppStack Overflow