Closed kakins closed 7 months ago
Just a follow up on this. After letting the app sit over the weekend, I've come back and it now loads fine, which confirms my connection to the store is correct. So definitely something was reset inside the app configuration store.
But as mentioned before, I definitely did not hit the 1k daily request limit. Also, I don't think bursts of request are the issue, since this is during app startup.
Ok I think this was based on a misunderstanding of the 24-hour time window. My metric query for "request over the past 24 hours" did not align with the time window of my quota restarting. Turns out we were in fact hitting our quota.
I'm using the .NET SDK to work with Feature Flags in ASP.NET Core.
The first thing I noticed is that app configuration is loading extremely slow all of the sudden, taking several minutes when normally it takes a few seconds. It hangs on the line
provider.Load()
inside ConfigurationManager, presumably encountering some sort of throttle and/or retries when configuration from ACS is being fetched.The method eventually completes, but this delayed behavior is causing my app service to timeout during startup in Azure.
However what I don't understand is why my requests would be throttled or even blocked. Here is my quota metric from my ACS instance -- where I am on the free tier with only one ACS instance in my subscription:
My understanding is I should get 1k requests/day. However, I am using far less than that. As you can see here I'm using about 150 requests per day.
And I have verified my connection string is valid multiple times.