i_like_eggs · Just an egg · ✭✭✭✭✭

You nailed it, John 😊 The aim is to make it visually engaging and operationally useful, something engineers have a reason to return to in their day-to-day work. Being able to filter the estate, select a node and inspect its metrics gives it that practical value. Keeping node identity and reported Orion status intact while…

Haha, I’ll take the Sheldon Cooper comparison 😂 Thank you @jaspiedad It grew out of the custom dashboard work I’ve been experimenting with inside SolarWinds and sharing with the community. It really started with “could I create a sphere of nodes and have them move around it?” From there, one idea led to another, and…

Thank you so much for this, and to everyone who joined the session. I had a lot of fun putting it together and may have gone slightly off-script once or twice 😅 I love the “case file of qualified evidence” description. That really captures what I was trying to show: moving beyond another alert and giving engineers enough…

Thanks mate, they have been really fun to build, thank you for spreading them 🤩

Done mate, good luck 🤞

Now we’re cooking 🍳 The bigger point is exactly it. The data was already there, but reshaping it live changes the questions you can ask and the patterns you can see. I wonder whether the next step is to layer in operational context: is this expected for that application, is it recurring, and is the change material enough…

Thank you so much, everyone! I genuinely appreciate you taking the time to join, all the engagement during the session and the lovely comments afterwards. I had a brilliant time sharing the dashboards and ideas with you all 😊🥚

Really interesting. The SolarWinds side stood out to me because there is already so much capability within Observability Self-Hosted. These are some of the capabilities I use today, rather than future ideas. With a different operating model, I use Observability Self-Hosted to correlate related observations across alerts,…

Below is an example of what one of those case files looks like. Before it reaches an engineer, SolarWinds has already grouped the repeated alerts, shown how the problem developed and identified the strongest place to begin investigating. It also clearly states what the available evidence does not tell us. (This entire…

I have a standard set of alerts that I use as a starting point when building a SolarWinds alerting framework. They cover the familiar areas: Node, interface and component status Polling failures CPU and memory usage Interface utilisation, errors and discards Response time Hardware sensors Routing neighbour status Volume…

Thank you all for your kind words :) @silverbacksays we never leave a man behind 🦍 ✌️

I may have got slightly carried away celebrating the Class of 2026… 😄 Genuinely honoured to be part of this class. Congratulations, everyone! 🏆

@naveensingh43 Your support made all the time and effort feel worthwhile. You backed what I was doing in a massive way, and I genuinely appreciate it. I honestly can’t thank you and @vinay.by enough 🤝 To be honest, I never expected my work to make any kind of difference or encourage engineers to look at things differently.…

I already miss the World Tour in London 😢 Hope you all have an amazing time!

😂 I know, I’m just stress-testing the MVP onboarding process before the NDAs land. So far, the banter layer has excellent resilience 🤭

A few jokers in the MVP ranks already… clearly I’m in good company 😂 Looking forward to working with all of you. Hope you’re ready for what I’ve got cooking 🍳

You nearly had me drafting my “former invitee MVP” LinkedIn post 😂❤️

Thank you friend, and you too 😜

You too mate 🙏

Thanks, really glad it helped. I’d be interested to see what you build for the network team :)

Thank you, mate. This one was special because it gives engineers clearer context on what to do next, based on defensible evidence :)

I really hope @SolarWinds is watching this space. The platform already has the data; the opportunity is in shaping it into clearer context, stronger evidence, and more defensible actions for engineers and customers. SaaS has its place, but self-hosted SolarWinds is still the real powerhouse for this kind of work. The…

I have a similar problem with SQL/SWQL-based alerts You can prove historical evidence fairly well. For example, a small node widget could show the distinct alert types that have triggered against that node, volume, or interface over the last 90 days. That at least gives you evidence that the object has been seen by…

Thank you, that’s really helpful. That route sounds like the cleanest fit for a small, safe lab. Really appreciate it

No worries at all, the egg appreciates the Grumpy Human guidance. I’m really just trying to keep this completely separate from employer/customer environments so I can test patterns cleanly without production baggage 🛄

I’m going to follow this one as well. If possible, please keep us updated on the outcome from support, as it would be useful to know what they find 😊

WOW, Massive thank you to the THWACK team. I genuinely never win anything, so seeing my name next to Prize 1 made my day. Really appreciate the effort that goes into these community missions, Looking forward to putting the Lenovo Armored Backpack to good use. Thanks again, THWACK crew.✌️

there may or may not be a small THWACK easter egg hidden in the rain... @amore1329 ✌️

Thanks All, I really appreciate it 😊 @vinay.by, your thought process on the execution is correct already. No custom JavaScript or external hosting services are involved. Taking a step back from SQL, CSS, HTML, or anything technical, the method I’ve been deliberately including across these examples is: Evidence → State →…

If I can be honest for a moment, and I might be wrong here - that’s fair - the 77% visibility figure is the one that really stuck with me. Not because it is surprising exactly, but because it feels very real. For me, visibility is not just about whether data exists somewhere in a platform. It is about whether teams can…