Blog Post

Tech Talk
3 MIN READ

December Product Power Hour Recap: Accelerating Troubleshooting with Automated Diagnostics

skydonnell's avatar
skydonnell
Icon for Community Manager rankCommunity Manager
2 days ago

In our final Product Power Hour of the year, we explored how Automated Diagnostics accelerates troubleshooting by adding real-time, actionable context to alerts. Ed and Patrick walked through configuration, execution models, and future enhancements while showcasing how diagnostics streamline triage and reduce MTTR. The session drew strong engagement, with customers expressing enthusiasm and offering thoughtful questions that helped clarify functionality and roadmap direction.

Key Highlights

⭐ Automated context at alert time  - diagnostics can run as soon as an alert triggers, giving teams immediate visibility into the issue without waiting for manual investigation.

⭐ Flexible execution workflows - diagnostics can be configured to run automatically, on-demand, or through escalation chains, enabling workflows that validate issues before ticketing.

⭐ Granular RBAC controls - separate roles for diagnostics and remediation ensure teams can restrict execution permissions as needed.

⭐ Service-level and multi-device diagnostics planned - customers highlighted the need to run diagnostics across multiple systems, which is already on the roadmap.

⭐ Community interest in shared modules - attendees expressed excitement for community-built diagnostics and future sharing mechanisms.

Q&A Highlights

Q: How will Automated Diagnostics integrate with Edwin AI?
A: First: getting the output of diagnostics into Edwin AI. Second: using that data to train Edwin AI’s models. Third: Edwin AI being able to execute diagnostics or remediation actions directly. That’s the pathway we’re heading toward.

Q: If we already have LM Logs integrations configured, can diagnostics leverage that data?
A: Yes. Right now, as far as automation goes, these would be triggered by data source alerts, but the plan is to extend that so they can be triggered by any type of alert, whether that’s from logs, configs, etc. The plan is to make these very extensible for any incoming data.

Q: Will Automated Diagnostics eventually run across multiple servers or services?
A:
Today, Automated Diagnostics is limited to automatically executing against the resource that went into the alert condition. Integrating this closely with our services is definitely part of our plans.

Q: Will diagnostics work on GA 39.001?
A: They will be able to run on GD 39.001. For more information, visit the release notes for 39.001 as the latest GD collector release.

Q: Can SSH-based diagnostic modules run on Linux devices monitored via SNMP?
A: Yes, diagnostics can run on devices monitored using SNMP as long as the collector has the correct access (e.g., SSH credentials) to execute the diagnostic.

Q: Are REST API calls allowed in diagnostic scripts?
A: Yes, and you can get really creative with REST API calls — essentially, you can write a Groovy script to do whatever you want.

Q: Are diagnostic permissions all-or-nothing today?
A: Yes. Users can either view and manage or see nothing.

Q: Will Role-Based Access Control (RBAC) for Automated Diagnostics and Automated  Remediation be separate?
A: Yes. Diagnostics and remediation permissions are separate, allowing organizations to grant diagnostic execution without allowing remediation actions.

Q: What license is required for Automated Diagnostics?
A:
Today, this feature is available as part of our new Advanced and Signature platform packages. Outside of that, if you're currently on an Enterprise package or something like that, there is an add-on that you could work with your CSM to talk through the details of that.

Customer Callouts

⭐ "I'm stupidly excited about these [features]. Can't wait for the demo."

⭐ "Definitely would be interested in any community modules people have made or are looking to make."

⭐ "This was great. Best demo I have had… really appreciate the live demo and answering all the questions so honestly and openly."

⭐ "Dashboarding is what makes LM better than all the other platforms for monitoring."

What’s Next

🎁 LogicMonitor 2025 Wrapped: Unified Observability Without Blind Spots

Join us for a special year-end event where we’ll unveil how LogicMonitor and Catchpoint joining forces transform LM Envision into the industry's leading AI-first observability platform. This session will cover:

  • A showcase of 2025’s biggest product announcements, platform advancements, and community impact

  • A first look at how LogicMonitor + Catchpoint delivers unified observability without blind spots

  • A preview of how this momentum sets the foundation for innovation in 2026

📅 Wednesday Dec 17, 12 pm CT
👉 Register here

🪵Logs for Lunch

Rapid Troubleshooting Using New Saved & Shared Queries
📅 Wednesday, Jan 14, 2026
🕙 10 AM PT / 12 PM CT / 1 PM ET / 6 PM GMT
👉 Register here

Additional Resources

If you missed any part of the session or want to revisit the content, we’ve got you covered:

Watch the recording below ⬇️

Published 2 days ago
Version 1.0
No CommentsBe the first to comment