Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Function app in Flex consumption plan not showing worker count in Azure portal diagnostic chart #10653

Open
anandsowm opened this issue Nov 25, 2024 · 5 comments
Assignees

Comments

@anandsowm
Copy link

For the Function apps that are in Flex Consumption plan , in the Diagnose and solve problems blade, for the 'HTTP functions Scaling' chart is not showing the worker instances count. However, in the corresponding AppInsights resource, for the direct kusto query as below, the instance count is correctly reported.

traces
| summarize dcount(cloud_RoleInstance) by bin(timestamp,30sec)
| render timechart

Region: West US 2

Expected behavior:

The instance count should be shown in the chart under the 'Diagnose and solve problem'

Actual behavior

As seen below, the instance count is not displayed.

Image
Image

@bhagyshricompany
Copy link

Hi @anandsowm Thanks for reporting please share the all steps for repro.

@anandsowm
Copy link
Author

Here are the steps for repro :

  1. Create a function app in Flex Consumption plan, with always ready instance as 1
  2. Deploy code for the function app with Http trigger, from Azure pipeline [in my case it is C#, .net8 isolated]
  3. Run the JMeter script that calls the Http trigger from multiple threads, duration of test can be 30min - 1hr
  4. Open the "HTTP functions scaling" chart from Diagnose and Resolve problems blade in Azure portal
  5. Notice that the "Number of workers allotted" trend is not reflecting the real number of worker instances launched during the above test run
  6. Open the App Insights resource associated with the function app, execute the kusto query mentioned in the issue, notice that the worker instances launched during the test run is correctly captured in 'traces' table.

@fabiocav
Copy link
Member

@nzthiago can you please help triage?

@nzthiago
Copy link
Member

nzthiago commented Dec 2, 2024

@anandsowm - thank you for reporting this. @FinVamp1 FYI to comment, who has been working to update those Diagnose and Resolve detectors to have values for Flex Consumption apps.

We're also working to have the Azure Monitor metric called "Automatic Scaling Instance Count" to be populated in the next few months.

@FinVamp1
Copy link
Member

FinVamp1 commented Dec 2, 2024

@anandsowm we're working on this and I will update the thread when the work is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants