Anomaly detection | Archive | LogicMonitor Community

DanAvni · 2017-04-26T05:33:06Z

We have a linux based http load balancer that is being monitored for a few months now. Yesterday we got a call from very few customers saying that our site was a bit slow. Looking on LM alerts I saw nothing so I thought that it must be some slow internet connection on the customer side or some other slow down on the internet connection of our hosting facility (so few customers complained that I did not seem to need any further investigation). Then about 5 hours after these calls I suddenly got a LM alert that the CPU of the http load balancer was too busy. Looking on the graph of the CPU of the load balancer I saw that the CPU was using 50-90% all the time for a few hours - starting when the customers complained (compared to about 10-20% on the same time previous week). Because the CPU usage changed all the time up and down LM did not trigger any alert for a few hours so I did not know something is wrong until a few samples triggered the alert. My suggestion: Have LM detect that something is not behaving as it normally does (compared to same period on weeks/months before). When an anomaly is detected it should be flagged with an anomaly color (I was thinking blue and a question mark icon) as it might be nothing but it could also be the first signs of a problem. I differentiate this from a warning alert as a warning is a definite value and this is just a speculation that something is not working as it normally does

MoreDiscussions