question

WiesingerRichard-4830 avatar image
2 Votes"
WiesingerRichard-4830 asked SwathiDhanwada-MSFT edited

Reached the trace writing limit of 100 events per minute

I have a .net core 3.1 web app deployed to an azure app service sending AppServiceAppLogs to a Log Analytics Workspace. This configured via Monitoring > Diagnostic Settings

This works but I get a maximum of 100 log messages per minute written to log analytics.
An additional warning log message is written: <app service name> has reached the trace writing limit of 100 events per minute.

I am not sure where this limit comes from and how to modify it.
Any help greatly appreciated.





azure-monitordotnet-aspnet-core-general
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

My team is seeing the same warning on .NET 6 as well. We also found this in the docs under the Managing your data volume section:

Throttling: Throttling limits the data rate to 32,000 events per second, averaged over 1 minute per instrumentation key.

32,000 events pers second is also what is indicated in the Azure Monitor Service Limits documentation, which is confusing and contradicts the "100 per minute" warning.

Any help/answers on this would be very useful.

1 Vote 1 ·

I have created a post in the product idea forum. Maybe you have time to upvote it there?
https://feedback.azure.com/d365community/idea/cb20fb1e-b6bc-ec11-a81b-6045bd796569

0 Votes 0 ·

Has there been any resolution on this? We are also facing the same issue "app has reached the trace writing limit of 100 events per minute"

1 Vote 1 ·

@WiesingerRichard-4830 @divya1388-7512 @BryanScheurman-5251 App Service Product Group team we confirmed that they are aware of this limitation and currently, we don't have an ETA to increase the quota related to the 100 logs per minute to be logged at the App Services.

0 Votes 0 ·
divya1388-7512 avatar image divya1388-7512 SwathiDhanwada-MSFT ·

@SwathiDhanwada-MSFT thank you for following up.

I have couple of questions:

       1. Is every log statement treated a trace event
       2. And is this the same behavior for app service logs writing to storage account?

Am also wondering if there are any alternatives for short term while the team comes up with a solution, as this is impacting our capability to proactively alert issues with our app.

Also since this issue is impacting many customers will MSFT priortize this bug fix

Thanks and Regards,
Divya

0 Votes 0 ·
Show more comments

0 Answers