Ago() not returning all rows or row limits for query?

%3CLINGO-SUB%20id%3D%22lingo-sub-137435%22%20slang%3D%22en-US%22%3EAgo()%20not%20returning%20all%20rows%20or%20row%20limits%20for%20query%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137435%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20running%20%3CBR%20%2F%3EAzureDiagnostics%3CBR%20%2F%3E%7C%20where%20TimeGenerated%26nbsp%3B%20%26gt%3B%20ago(91d)%3CBR%20%2F%3E%7C%20where%20ResourceType%20%3D%3D%20%22APPLICATIONGATEWAYS%22%20and%20OperationName%20%3D%3D%20%22ApplicationGatewayPerformance%22%20%3CBR%20%2F%3E%3CBR%20%2F%3EHowever%2C%20I%20am%20not%20getting%20more%20than%2012%20days%20%22ago%22%20of%20data.%26nbsp%3B%20Is%20this%20a%20limit%20to%20the%20tool%2C%20am%20I%20hitting%20a%20row%20limit%2C%20or%20is%20there%20a%20historical%20limit%20to%20how%20much%20data%20I%20can%20pull%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20doing%20the%20export%20to%20Power%20BI%20M%20query%20and%20running%20it%20from%20there.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-137435%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139283%22%20slang%3D%22en-US%22%3ERe%3A%20Ago()%20not%20returning%20all%20rows%20or%20row%20limits%20for%20query%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139283%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20tried%20similar%20queries%20on%20our%20test%20data%20and%20I%20wasn't%20able%20to%20reproduce%20this%20behavior.%20Changing%20the%20Ago%20parameter%20changed%20the%20end%20results%20even%20in%20high%20numbers.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%2C%3CBR%20%2F%3EMeir%20%3A%26gt%3B%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137530%22%20slang%3D%22en-US%22%3ERe%3A%20Ago()%20not%20returning%20all%20rows%20or%20row%20limits%20for%20query%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137530%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECould%20you%20please%20add%20a%20%22%7C%20count%22%20at%20the%20end%20of%20your%20query%20to%20confirm%20how%20many%20rows%20are%20being%20returned%3F%20The%20Log%20Analytics%20UI%20will%20cut%20you%20off%20at%2010%2C000%20and%20when%20importing%20to%20Power%20BI%2C%20you'll%20be%20limited%20to%20500%2C000%20rows%20or%20Power%20BI's%20data%20model%20limit.%20If%20this%20is%20not%20the%20case%2C%20please%20let%20us%20know%2C%20and%20we'll%20dig%20into%20what%20else%20the%20issue%20might%20be.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3E-Evgeny%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I am running
AzureDiagnostics
| where TimeGenerated  > ago(91d)
| where ResourceType == "APPLICATIONGATEWAYS" and OperationName == "ApplicationGatewayPerformance"

However, I am not getting more than 12 days "ago" of data.  Is this a limit to the tool, am I hitting a row limit, or is there a historical limit to how much data I can pull?

 

I am doing the export to Power BI M query and running it from there.

 

Thanks!

2 Replies
Highlighted

Hi,

 

Could you please add a "| count" at the end of your query to confirm how many rows are being returned? The Log Analytics UI will cut you off at 10,000 and when importing to Power BI, you'll be limited to 500,000 rows or Power BI's data model limit. If this is not the case, please let us know, and we'll dig into what else the issue might be.

 

Thanks,

-Evgeny

Highlighted
Hi,

I have tried similar queries on our test data and I wasn't able to reproduce this behavior. Changing the Ago parameter changed the end results even in high numbers.

Thanks,
Meir :>