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 searche...
Hi @KrzysztofRadomski and thank you for your feedback.In Log Analytics,
the entire query (including functions used within) is effected by the
time picker.The functions used within a query don't run in a different
'container' or scope - but run with the same context. This means that
time filter in th...
The new approach is troublesome when using functions in saved searches.
When invoking a function from a query, time picker sets by default "Set
in query" while there is no query-set time range in a parent query
rather than within a function. It's confusing because I obviously cannot
see what time ra...
You are correct on your options. regarding performance issues, I have
tested the feature with several environments and many early onboarders
to our private preview, and couldn't find any performance penalties.
Please note that this service is still in public preview, with support,
and we still work ...
Latest Comments