Forum Discussion
Ignore bucket based on offset
- Feb 25, 2020
I suspect you have values below 300,000 due to the time you run the query, if it runs in the morning lets say 9am, you get a small count from midnight to 8am that day (where as the previous whole day will always have more results)- hence the lower number.
Heartbeat | where TimeGenerated between (startofday(ago(2d))..startofday(ago(0d))) | summarize Rows=count() by bin(TimeGenerated, 1h) | render timechart
This would be a example to get two whole days (midnight to midnight), to get rid of those two varying data points. I'm a fan of "startofday" for this reason. https://docs.microsoft.com/en-us/azure/kusto/query/startofdayfunction
I suspect you have values below 300,000 due to the time you run the query, if it runs in the morning lets say 9am, you get a small count from midnight to 8am that day (where as the previous whole day will always have more results)- hence the lower number.
Heartbeat
| where TimeGenerated between (startofday(ago(2d))..startofday(ago(0d)))
| summarize Rows=count() by bin(TimeGenerated, 1h)
| render timechart
This would be a example to get two whole days (midnight to midnight), to get rid of those two varying data points. I'm a fan of "startofday" for this reason. https://docs.microsoft.com/en-us/azure/kusto/query/startofdayfunction