Log Analytics time picker is an easy way to scope and control the query's time scope - directly from the UI without composing or altering your query code.
Time picker is also a great way to narrow ...
Updated Apr 08, 2022
Version 2.0
Blog Post
Hi RoyGal ,
Thank you for your reply. But it doesn't explain why the timepicker resets to "Set in query" timerange when external function is in use. It doesn't make sense and, if I'm not vigilant to always remember to set the timepicker to some arbitrary time span, the whole history will be searched as if there was no timerange at all. It did not work like this before last changes and it was better, as the timepicker setting were set to 24h by default and retained between edits.
I found just another curiosity after last timepicker-related changes. Let's assume following query:
Heartbeat | summarize MinTime=min(TimeGenerated), MaxTime=max(TimeGenerated), TimeDifference=(max(TimeGenerated)-min(TimeGenerated)) by Computer
Looks good. But when you type it in, see what timepicker says:
Where, for Odin's sake, does the editor see the query-set timerange? It's beyond me. When run, whole history is searched, returning the earliest heartbeat available.
Regards,
Krzysztof Radomski