Share via

Getting "Daily Quota Exceeded" with Azure Monitor OpenTelemetry Exporter and Node.JS

Alexandre Silva 20 Reputation points
2025-05-08T18:36:40.6233333+00:00

Hi all,

I have some pods running Node.JS and the Azure Monitor OpenTelemetry Exporter in AKS, sending data to Application Insights via instrumentation key.

Recently many log entries started to appear with "Daily Quota Exceeded", however the services do not reach more than 5GB of logs.

Here's the sample log:

{"stack":"Error: PeriodicExportingMetricReader: metrics export failed (error RestError: {"itemsReceived":4,"itemsAccepted":0,"appId":null,"errors":[{"index":0,"statusCode":439,"message":"Daily quota exceeded"}

I've already checked the cap limits in Application Insights and in the Log Analytics Workspace, and it is far from what is configured there (100GB/day)

Any idea of what could be happening?

Many thanks

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,590 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Suwarna S Kale 2,591 Reputation points
    2025-05-08T19:28:37.1766667+00:00

    Hello Alexandre Silva,

    Thank you for posting your question in the Microsoft Q&A forum. 

    The "Daily Quota Exceeded" error in Azure Application Insights, despite being below the configured 100GB/day limit, typically indicates an ingestion throttling issue rather than a true quota breach. This can occur if: 

    • Sampling is misconfigured - Application Insights may enforce adaptive sampling, dropping logs even if the total volume is low. 
    • A burst of telemetry triggered rate limiting - Azure enforces short-term ingestion caps to prevent spikes. 
    • The instrumentation key (IK) is shared across multiple apps, causing cumulative throttling. 
    • Logs contain excessively large payloads, hitting size-based limits before volume-based ones. 

    To resolve this, disable adaptive sampling in your OpenTelemetry config, verify no IK reuse exists, and check per-second ingestion limits in Azure Monitor. If throttling persists, switch to a Workspace-based Application Insights model, which offers more flexible quotas. 

    If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated. 

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.