Always Ready Instance Count for Flex-Consumption Plan.

Hi Amal Syed,

Thanks for posting your question in Microsoft Q&A forum

In a Flex Consumption Plan for Azure Functions, when you enable the Always Ready feature for HTTP triggers, it ensures that the function app is always ready to handle incoming HTTP requests without a cold start delay. This means that a certain number of instances will remain always ready and running, which helps to reduce response times.

Based on the images you provided, it looks like your Always Ready Units metric is showing a count that spikes between 5-6. This suggests that, at certain times, 5-6 instances are being kept always ready to handle HTTP requests. These spikes represent the number of Always Ready instances at any given time.

1.Always Ready Units Spiking: When you see a spike in the Always Ready Units metric between 5-6, it indicates that you have that many Always Ready instances running. Yes, you will be billed for all of them as they are actively allocated for your app. The purpose of this is to reduce cold start times for your HTTP-triggered functions, ensuring they're ready to handle incoming requests more quickly. The total number of executions. In always ready billing, there are no free grants.

The minimum billable execution period for both execution modes is 1,000 ms. Past that, the billable activity period is rounded up to the nearest 100 ms. You can find details on the Flex Consumption plan billing meters in the Monitoring reference.

For details about how costs are calculated when you run in a Flex Consumption plan, including examples, see Consumption-based costs.

You can refer to Azure's pricing documentation for detailed costs related to Always Ready instances in a Flex consumption plan

• Estimating consumption-based costs in Azure Functions | Microsoft Learn
• Pricing - Functions | Microsoft Azure

2.Queue-based Trigger Functions: Currently, the Always Ready configuration is specifically available for HTTP and other specific trigger types like Durable and Blob triggers. Unfortunately, as of now, there isn't a way to configure Always Ready for Queue-based functions via the Azure portal or Azure CLI.

Refer document: Azure Functions Flex Consumption plan hosting | Microsoft LearnI hope this helps do let me know if you have any questions on this

Thanks for explanation.
In this case, what significance does the count 1 which we configure have?