<!channel> when you folks are debugging, how often do you use SigNoz? What do you feel we can improve for you there? And this is more of a related question for debugging regardless of whether you use SigNoz or not – how do you come up with hypotheses and how do you go about discarding the wrong ones? I'm curious to learn more about the debugging process.

Getting people to use SigNoz has been my biggest issue. So far the biggest thing for us is that I wish we could go from Dashboards (which support dynamic variables) into Logs without losing the context

+100 to carlos’s point. when there’s e.g some issue with memory pressure, I want to dig into when the memory pressure happened in the dashboard, and then pivot to the logs at that time

Something like this would work in that case 👀

my company loves signoz since it doesnt require any licensing or renewal like other app. the trouble we face is usually the lack of information in documentations, for debugging our teams asked chat gpt and slack community a lot and yet still feel like searching trough needle stack. our users love the service map because not everyone understand IT stuff and its help a lot when trying to figure out RCA. but to read / filter trace logs is quite challenging because its quite confusing and need a lot of detailed explanation and research.