<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident on SystemsGolive</title><link>https://systemsgolive.com/tags/incident/</link><description>Recent content in Incident on SystemsGolive</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 systemsgolive.com and Mickael Asghar. All rights reserved.</copyright><lastBuildDate>Tue, 10 Sep 2024 16:44:01 +0100</lastBuildDate><atom:link href="https://systemsgolive.com/tags/incident/index.xml" rel="self" type="application/rss+xml"/><item><title>Dealing with False Ping Alerts in LogicMonitor: Building a Fallback Ping Monitoring Script for Production VMs</title><link>https://systemsgolive.com/post/implementating-backup-ping-monitoring-solution/</link><pubDate>Tue, 10 Sep 2024 16:44:01 +0100</pubDate><guid>https://systemsgolive.com/post/implementating-backup-ping-monitoring-solution/</guid><description>
On Friday 6th September 2024 at 21:31, we received an alert from LogicMonitor indicating one of our production web app servers (Tomcat#3) was down, with the message: "The host Tomcat#3 (i-xxxxxxx) is down". However, shortly after receiving the alert, we attempted to SSH into the VM and confirmed that the server was fully operational. But what did it go wrong?</description></item></channel></rss>