We have an application that has a mix of on-premise static infrastructure and newer services running in Azure. We recently implemented a new .Net Core service as an Azure App Service with autoscaling. The new service is appearing fine in our application flow map, but the node count is just increasing for every scale-up event, and not decreasing on scale-down. Right now, it looks like we have 97 nodes, when in reality it's running at between 6-8 depending on load. Is there a way to manage this automatically so the node count is correct for this service, preferably without static on-premise nodes disappearing through inactivity during quieter processing periods?
... View more