3 ms·
I only ever need to know KQL when something isn't working well, which turns 1 problem into 2: the original problem, and how to express exactly what I need in a
by barryrandall 2y ago
I only ever need to know KQL when something isn't working well, which turns 1 problem into 2: the original problem, and how to express exactly what I need in a language that, when things are going well, I forget quickly.
- bbkane 2y agoI've definitely had my troubles with KQL, but I still find it more memorable than SQL. Interesting that some folks feel the opposite. My most recent favorite KQL trick for debugging from logs is `autocluster`. Maybe you'll also find it useful when you're in trouble :)