We are using Application Insights in our application for monitoring purposes.
Today we received a message, that we exceeded the rate limit of 86,400 requests per day (https://dev.applicationinsights.io/documentation/Authorization/Rate-limits).
To analyze the cause of the problem I would like to know the origin of those requests. Is it possible to do this either in the azure portal or any other way?
You can examine requests/dependencies/other documents in Application Insights Analytics and check from their content who sent them.
union *
| order by timestamp
| take 1000
Related
So I am testing Azure App Configuration.
https://learn.microsoft.com/en-us/azure/azure-app-configuration/quickstart-dotnet-core-app
I am trying free plan for this, which has 1000 requests limit.
My App Config store would have somewhere around 50 configs stored in it, which I retrieved in my startup.cs file, which, I guess is loaded only once when I start my Azure Functions.
But to my surprise, after testing it for a couple of times, it's returning 429 - Request throttled.
So my question is, how Azure counts request to App Config? Is it per store or per config key-value?
Requests to App Configuration is counted per store. Given you have 50 config settings, they should be all retrieved with just one request. You may like to check the "total request count" graph on the overview page of the Azure portal to learn more of your usage. The link below also has a few suggestions about how to reduce the requests.
https://learn.microsoft.com/en-us/azure/azure-app-configuration/howto-best-practices#reduce-requests-made-to-app-configuration
I have ASMX webservice with 1 MSSQL Database and a Single Table.
I have currently deployed it to Azure in the App Service
I have upgraded from Free Trial to Pay Per Use Plan.
I'm really confused with the App Service Plan
The ASMX Service is called by a Desktop application and it only has a few methods,just to fetch and return data from database.At max 100 users will be using it and may be a maximum of 1000 method calls may be made.
What does 60 minutes/day mean? The webservice can function for only 60 minutes?
I'm really confused.Please advice
Think of the minutes listed similar to a consumption plan on Azure Functions. When your website is responding to requests, it active and your "on the clock." When the site has been idle for a while, it will effectively go to sleep and you are "off the clock." Free and shared tiers are not "Always On". If your compute minute usage exceeds the quota (60 or 240 minutes), then Azure will return a 403 message to the browser and your site is unavailable until the quota resets for the next day. Free and Shared plans are really not designed for production. If you think you can squeeze your 1000 method calls into those time limits, great...it may be a cheaper solution. But you should expect the possibility of a 403 being returned and your request not being fulfilled. If your desktop app is important and really needs this service, you are probably better off paying for Basic (B1).
I have an app service plan which is hosting 2 Web APIs, the issue I am facing is that I am unable to view details such as: CPU Usage, Memory Percentage, Requests, Average Response time etc.
These can be found under the Overview tab for both App Service and App Service Plan but no data is being recorded, even if I retrieve data for the whole week rather than the last hour only.
I have also confirmed that I am hitting the correct App hosted on the correct Plan. Have I missed anything? Do I need to enable something?
I have also generated around 20k requests in the last few hours so I expect something to show up.
I am trying to get a list of all Storage Accounts present in my Azure subscription but I am getting a throttling error.
com.microsoft.azure.CloudException: Status code 429, {"error":{"code":"ResourceCollectionRequestsThrottled","message":"Operation 'Microsoft.Storage/storageAccounts/read' failed as server encountered too many requests. Please try after '17' seconds. Tracking Id is 'e982a894-0f3e-4291-a9b3-e147c18f8f60'."}}
The request prior to this request prints there are 13869 more remaining subscription reads but it still fails.
x-ms-ratelimit-remaining-subscription-reads: 13869
There are around 60 Storage Accounts in my subscription and that according is a small number.
Any idea what's causing this and that too only while listing Storage Accounts and nowhere else.
According to this article:
For each subscription and tenant, Resource Manager limits read requests to 15,000 per hour and write requests to 1,200 per hour. These limits apply to each Azure Resource Manager instance; there are multiple instances in every Azure region, and Azure Resource Manager is deployed to all Azure regions. So, in practice, limits are effectively much higher than those listed above, as user requests are generally serviced by many different instances.
If your application or script reaches these limits, you need to throttle your requests.
So if you reach the request limit, Resource Manager returns the 429 HTTP status code and a Retry-After value in the header. The Retry-After value specifies the number of seconds your application should wait (or sleep) before sending the next request. If you send a request before the retry value has elapsed, your request is not processed and a new retry value is returned.
I suggest you could use this way to get the number of the read time. If it will meet the limit, you could write codes to limit the application to send the request.
I am trying to use application Insights API get some telemetary and use it in my website.
During my testing i navigate to some pages in website and then call api but that doesnt get the latest pages i go to
Is there any setting that should be done on azure to make make api get latest pages ?
You should expect a delay between the data generation and data available for querying. Typically latency is in single minutes range. And it is typically smaller for metrics than for raw events.
SLA for Application Insights is 2 hours:
"Data Latency" is the number of minutes that data received from the instrumentation in Customer’s application is delayed from appearing in Application Insights service where the delay is greater than 2 hours.