App service automatic scaling httplogs / application insights 404

Cloudy 226 Reputation points
2025-02-25T14:17:50.8566667+00:00

Dear all,

Need your help regarding the 404 errors logged because of azure app service automatisc scaling poller (visibly...)

Following the documentation, i'm not able to found the same entries (404 on / and 80).

User's image

The only one explained is /admin/host/ping but nothing shown :

https://learn.microsoft.com/en-us/azure/app-service/manage-automatic-scaling?tabs=azure-portal#why-does-appservicehttplogs-have-log-entries-similar-to-adminhostping-with-a-404-status

How to avoid that / rewrite or make the documentation up2 date ?it seems that ElasticScaleControllerExtension is related to premium Azure function;...(when googled it)

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,939 questions
{count} votes

Accepted answer
  1. Shree Hima Bindu Maganti 4,775 Reputation points Microsoft External Staff Moderator
    2025-02-25T18:04:38.8933333+00:00

    Hi Cloudy,
    Thanks for reaching here!
    The 404 errors you're seeing in your App Service logs are caused by Azure's automatic scaling poller, specifically the Elastic Scale Controller Extension (ElasticScaleControllerExtension/2.0.29.0). This is an internal Azure process that occasionally sends GET requests to check instance availability for auto-scaling.

    These 404 responses are expected and do not impact scaling performance or security. Azure’s scaling decisions are based on CPU, memory, and response time, not these requests. The only status code that affects scaling is 429 (Too Many Requests), while scale-out decisions are primarily determined by latency.

    Previously, this behavior was discussed when automatic scaling was in preview, but that is no longer the case. Microsoft has confirmed that these 404 errors are expected because the scaling monitor currently pings the same endpoint for both Function Apps and Web Apps. However, an upcoming release will modify this behavior by using a different endpoint for Web Apps, which should help reduce unnecessary logging.

    At this time, there is no direct way to disable or rewrite these requests. If these logs are causing issues, you can filter them out in Application Insights to minimize noise. There is no security concern associated with these requests, as they originate from the same scale unit that hosts the app.

    Health Check Endpoints in Azure App Service
    https://learn.microsoft.com/en-us/answers/questions/1457153/seeing-a-lot-of-404s-to-admin-host-ping-after-turn
    Filtering telemetry in Application Insights

    https://stackoverflow.com/questions/79303286/most-recommended-approach-to-handle-404-errors-to-admin-host-ping-for-my-asp-ne
    Let me know if you have any further assistances needed.
    If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.