Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
When I query my Log Analytics workspace, the returned results are missing "windows" of data at various locations in the results table. Here is my kusto query in LA:
Event | where EventLog == "Talon" | search EventData contains ":Filename=TafsMtPt:" | parse RenderedDescription with "Result=" Result ":error=" Error ":Peer=" Peer ":Direction=" Direction ":Mode=" Mode ":Filename=TafsMtPt:" Filename ":File Size=" FileSize ":Bytes Exchanged=" BytesExchanged ":Transfer Efficiency=" TransferEfficiency ":SID=" UserSID | project Computer, Result, Error, Peer, Direction, Mode, Filename, FileSize, BytesExchanged, TransferEfficiency, UserSID, TimeGenerated, EventLevelName | project-rename EventTime = TimeGenerated, LogType = EventLevelName | where Filename !contains "-temp." and Filename !contains "desktop.ini" and Filename !contains "~$" and Filename !contains ".tmp" and Filename !endswith "_placeholder_"
When I run this query in the Azure portal, I get complete results, with no missing data. Visualizing the results in a Log Analytics workspace summary by counting the number of events in hourly bins, you see spikes in the number of events for each weekday.
But when I export the kusto query to M Query for Power BI, the resultant data set is missing a significant amount of data. Two of the weekday peaks are missing entirely.
I am using the latest edition of Power BI desktop. What on earth is going on here?
Solved! Go to Solution.
I resolved this. My missing data was due to a results table that violated the 64,000,000 bytes maximum enforced by the Log Analytics API. I will have to re-architect my queries with this limitation in mind. The Log Analytics API limitations are documented here:
https://dev.loganalytics.io/documentation/Using-the-API/Limits
I resolved this. My missing data was due to a results table that violated the 64,000,000 bytes maximum enforced by the Log Analytics API. I will have to re-architect my queries with this limitation in mind. The Log Analytics API limitations are documented here:
https://dev.loganalytics.io/documentation/Using-the-API/Limits
Hi @jholl016 ,
Based on my test, I cannot reproduce your issue here. I recommend you to create a support ticket for help if you are a pro user.
https://powerbi.microsoft.com/en-us/support/
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 46 | |
| 42 | |
| 34 | |
| 31 | |
| 21 |
| User | Count |
|---|---|
| 134 | |
| 124 | |
| 98 | |
| 80 | |
| 65 |