Our healthcare community came together for a practical, customer-led conversation on what observability looks like in real hospital environments. Our pilot healthcare-specific session featured a walkthrough from Matt Whitney , followed by open discussion and peer sharing. Session highlights How NYP approaches application, server, and network observability today Where healthcare environments hit unique monitoring gaps (especially clinical and vendor-owned devices) What teams are doing to reduce alert noise and speed up incident routing A new Healthcare User Group space launching in the LogicMonitor Community for continued collaboration Customer spotlight: NYP’s observability journey Matt shared how NYP is using LogicMonitor across core infrastructure and applications, including: Discovery-driven monitoring and environment organization (with grouping to support operational ownership) Event and log-based visibility for Windows application servers Selective use of synthetic monitoring and URL checks, typically applied case-by-case The key takeaway: teams can build strong coverage, but standardizing application monitoring across many app types and owners remains a consistent challenge. What the group leaned into 1) Standardizing application monitoring (without overengineering) Participants compared approaches for getting beyond “server-only” monitoring. Common themes: Start with repeatable baselines (availability, key Windows events, core service checks) Expand with app-specific signals where teams can reliably source logs or metrics Use synthetic checks strategically, especially where login flows and workflow complexity increase effort 2) Monitoring clinical and vendor-owned equipment The most healthcare-specific pain point: radiology and other clinical devices, where vendors expose limited telemetry. The group discussed the reality that many teams are stuck with basic up/down status and the need for shared patterns to support deeper health indicators. 3) Alert management, correlation, and change awareness The discussion shifted from “more alerts” to “better alerts”: Interest in correlation approaches that reduce downstream noise during upstream failures Aligning monitoring and incident workflows with change activity, so teams can suppress or de-emphasize expected noise during approved work Where LogicMonitor capabilities help today, and where teams are still stitching together processes across tools 4) Incident routing and on-call execution with ServiceNow plus external tooling Several attendees noted that ServiceNow handles assignment and escalation, while paging and on-call execution may be handled by a dedicated alerting tool. The common goal: ensure the right responder is notified quickly, with clear rules when an on-call does not acknowledge. What’s next: keep the conversation going To carry the momentum forward, we’re launching a dedicated Healthcare User Group space in the LogicMonitor Community. This will be the place to: Share healthcare-specific monitoring patterns (especially for clinical devices) Compare ServiceNow and alerting integrations Post example data sources, dashboards, and escalation strategies Collect “what works” playbooks that others can adopt Thanks again for joining us and contributing to a valuable discussion. We’re looking forward to continuing the conversation in the Healthcare User Group.
