microsoft / microsoft/finops-toolkit
Main view hits 500k KQL limit for a 30 day period, thus not showing data anymore
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 249
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
🐛 Problem
When viewing a month in FinOps hub, I get the error message:
"Underlying Error: QueryUserError
More details: Expression.Error: Query execution has exceeded the allowed limits (80DA0003): The results of this query exceed the set limit of 500000 records, so not all records were returned (E_QUERY_RESULT_SET_TOO_LARGE, 0x80DA0003). See https://aka.ms/kustoquerylimits for more information and possible solutions..
[0]Kusto.Data.Exceptions.KustoServicePartialQueryFailureLimitsExceededException: Query execution has exceeded the allowed limits (80DA0003): The results of this query exceed the set limit of 500000 records, so not all records were returned (E_QUERY_RESULT_SET_TOO_LARGE, 0x80DA0003). See https://aka.ms/kustoquerylimits for more information and possible solutions.."
👣 Repro steps
- Go to Resources
- Select time period for 30 days
- See error: both visuals are shown as error
🤔 Expected
To see the chart and entries with their costs
📷 Screenshots
🔧 Environment
- FinOps hub version: (e.g., 0.10, 0.11, 12.0, 13.0)
- Billing account type: EA (Enterprise Agreement)
- Power BI report type: ADX (Azure Data Explorer)
- Cost Management export: FOCUS 1.0 r2
ℹ️ Additional context
It worked in the past, but since this month it looks like to be too much data
🙋♀️ Ask for the community
- Please vote this issue up (👍) to prioritize it.
- Leave comments to help us solidify the vision.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in the Resources view using the ADX Power BI report, FOCUS 1.0 r2 export, and a 30-day period. Start by tracing the KQL query behind the two failing visuals and identify why the result exceeds 500,000 records. Done means the chart and cost entries render for the reported scenario without the query-limit error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- analytics, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100