Logs in Application Insights only collecting until just after 9am every day. Daily caps is off.

Lars Lohndorf-Larsen 0 Reputation points
2026-09-07T13:38:47.6933333+00:00

I do a simple query in Application Insights logs like this:

traces
| where timestamp > ago(1d)
| order by timestamp desc 

Sorry I could not find a good tag for this, so please reroute if needed.

Every day the last log entry I get is from just after 9am (the exact time varies a little bit).

I have checked that the daily cap is off on the application insights.

The same happens for the other Application Insights accounts.

Is there another place where there could be a cap?

Azure Advisor
Azure Advisor

An Azure personalized recommendation engine that helps users follow best practices to optimize Azure deployments.

0 comments No comments

1 answer

Sort by: Newest
  1. SHOUMIK CHAKRAVARTY 580 Reputation points
    2026-09-07T16:25:54.56+00:00

    Hi @Lars Lohndorf-Larsen ,

    The pattern you are seeing, where logs are collected until roughly the same time every day and then stop for the rest of the day across multiple Application Insights resources, points to one specific cause. It is almost always the daily data cap on the Log Analytics workspace, not the cap on the Application Insights resource.

    For workspace‑based Application Insights, there are two separate daily caps:

    one on the Application Insights resource

    one on the Log Analytics workspace

    The effective cap is whichever of the two is lower. Turning off the cap in Application Insights only disables that resource’s cap. It does not disable the workspace cap. If several of your Application Insights resources send data to the same workspace, a workspace‑level cap would explain why all of them stop at the same time.

    Check the workspace daily cap

    Go to:

    Log Analytics workspace → Usage and estimated costs → Data cap

    Check whether a cap is set and look at the reset hour shown on that page. The reset hour is fixed per workspace and cannot be changed. If that reset hour matches the time when your logs stop, for example just after 9am, it fits your symptoms exactly. Ingestion resumes at reset, a burst of data arrives, the cap is hit again almost immediately, and ingestion stops until the next day. This produces the daily cutoff you are seeing, with slight variation depending on how quickly the post‑reset burst crosses the threshold.

    Check ingestion status directly

    Run this query in the workspace:

    _LogOperation
    | where TimeGenerated >= ago(2d)
    | where Category == "Ingestion"
    | where Level in ("Warning", "Error")
    | order by TimeGenerated desc
    

    This is the documented way to check ingestion health. If you see warnings or errors around the same time each day, that confirms the cap is being hit.

    If the workspace cap is off

    If the workspace cap is also disabled, check whether the Application Insights resource is still linked to the workspace under Application Insights → Properties → Workspace. You can also run a workspace query with an explicit date range to rule out a portal display issue.

    Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

    Was this answer helpful?


Your answer

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