<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Metrics on SystemsGolive</title><link>https://systemsgolive.com/tags/metrics/</link><description>Recent content in Metrics on SystemsGolive</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 systemsgolive.com and Mickael Asghar. All rights reserved.</copyright><lastBuildDate>Fri, 23 Aug 2024 22:05:29 +0100</lastBuildDate><atom:link href="https://systemsgolive.com/tags/metrics/index.xml" rel="self" type="application/rss+xml"/><item><title>LogicMonitor: Understanding Why CPUBusyPercent Alert Was Not Triggered</title><link>https://systemsgolive.com/post/logicmonior-cpubusypercent-alert/</link><pubDate>Fri, 23 Aug 2024 22:05:29 +0100</pubDate><guid>https://systemsgolive.com/post/logicmonior-cpubusypercent-alert/</guid><description>
On 15th August 2024, an incident occurred where the `CPUBusyPercent` alert did not trigger for one of our Production MySQL Database VMs (DB01), despite the CPU being at 100% for seven minutes. This was unexpected since the threshold settings in LogicMonitor were supposed to trigger alerts under such conditions.</description></item></channel></rss>