“the waldo way”
So.. I need a Mandalorian helmet for this one .. wait .. I HAVE one! 🤪 You know the line they keep repeating: “this is the way“. And the funny thing about…
So.. I need a Mandalorian helmet for this one .. wait .. I HAVE one! 🤪 You know the line they keep repeating: “this is the way“. And the funny thing about…
Ok .. so .. I’ve been sitting on this one for a while.. A few months back, I got pulled into something Microsoft was cooking around “performance” .. and thanks to the…
I did a thing .. again .. 🤪 A few weeks ago I wrote about building the tool but forgetting the skill. That post kept nagging at me. And the more I thought about…
So.. here is a train of thoughts… I’ve been doing this telemetry stuff for a while now. KQL snippets, ADE (or what I recently learned: the real abbreviation is “ADX” 🙈) dashboards,…
Next topic in the troubleshooting series: Telemetry. Probably the biggest one yet – and one that’s quite close to my heart, as I’ve been spending a ridiculous amount of time on it over…
A while ago I wrote about the BCTalent Escape Room app, and why we built it: I don’t have too much time for my monthly blog post (yep, it’s something I have…
TL;DR While showing my kid what I was working on, I casually asked my BC Telemetry Buddy “what customer has the most reason to complain” – and accidentally discovered a customer bleeding CPU…
I did a thing … well .. I guess .. I kept doing things .. 🤪 If you haven’t read my previous post, I recommend to do so: Analyzing BC Telemetry with…
I did a thing … TL;DR I created an MCP for VSCode that makes it possible for you to just “talk” to your Telemetry without touching KQL or getting to know any…
Next topic in this series: the Event Recorder. “This Series”, you might wonder? Yes: I’m doing (slowly but steady) a series on anything “troubleshooting tools” including “my own view” on the different…
We use cookies to improve your experience on this site. By continuing to browse, you agree to our use of cookies.
