How Do You Capture & Revisit Your Investigations? (Where Does It Break?) | Product Discussions

Ian Marge · 2026-03-23T16:53:24.372272Z

Hi LogicMonitor Community,I’m part of the LogicMonitor product team, and we’re researching how teams investigate incidents and just as importantly, how that work gets preserved (or lost) over time.In many environments, investigation context ends up spread across dashboards, queries, tickets, screenshots, and docs. We’re trying to better understand how this works for you today and where it breaks down.When you're investigating incidents or performance issues:How do you capture what you reviewed (queries, dashboards, alerts, time ranges) so others can understand or revisit your work later?How often do you need to revisit or re-run past investigations, and how easy or painful is that process today?Where does context typically get lost during or after an investigation?What tools or workflows do you rely on today, and what don’t they do well?What makes it difficult to trust or reuse past analysis when similar issues come up again?We’re also exploring a concept around making investigations easier to revisit:If you could go back and see an investigation exactly as it was (same queries, time ranges, and context), how would that change your workflow?Your feedback will directly shape how we think about improving investigation and collaboration workflows in LogicMonitor. Even quick examples or high-level thoughts are incredibly helpful.Feel free to reply here or message me directly if you prefer. Thanks in advance for helping us build something truly useful for this community. Best,Ian

MoreDiscussions

How Do You Capture & Revisit Your Investigations? (Where Does It Break?) | Product Discussions | LogicMonitor Community