Do Static and Dynamic thresholds work together?
Hi, I don't understand Dynamic thresholds and the weird UI to set them up. The whole thing about band factors and things make no sense to me. Here's my specific scenario and maybe someone can tell me the best way to handle this. We have a server that spikes it's CPU up pretty high every weekday morning. Generally starts around 5AM and ends around 9-10AM. Some days (Fridays) it seems to go longer. We don't want to get any alerts when it does this. Here's the graph for December (even though it looks like the spikes only go to 60, they actually all go to 99 or 100 when zoomed in more): We tried setting a daily, recurring SDT, but that still shows the errors, it just doesn't notify us about them. We want LM to consider the morning Spikes as "normal" and to ignore them. We setup a Dynamic Threshold to see if that would help. Here's a screenshot of what that looks like: As you can see by the arrow, this doesn't seem to have "Learned" what normal is. It seems like it just waits for the CPU to spike and then adjusts the "Expected Range" to compensate. If it was actually Learning, it should have expected the spike, since it happens every weekday, and adjusted BEFORE it happened. Right? Also, we have the standard Static Thresholds also enabled so we alert at 90/95/98 for this server. We get alerts for it all the time and aren't sure how to properly set this up. If we use the Dynamic alerts, should we turn off the Static ones since one doesn't seem to override the other? Should the Dynamic expected range know that the morning spike is going to happen or is that not how dynamic thresholds work? We rarely use them because we just don't get how to use them properly even after reading all the KBs and such. Any ideas, opinions, etc would be great.Dynamic vs Static Thresholds?
Hi, I've been using LM for years and have never really understood Dynamic Thresholds and when to and when to not use them. How do they work in conjunction with Static thresholds or should you only use one or the other. Here's the specific issue I'm working on right now. I have a server that spikes the CPU all the time during the day. Here's the current graph for this device: What we want LM to do is "learn" that from 5AM to 5PM (or whatever it is), that the CPU is normally high during this range and to not alert us. But in between those those times, and on weekends, it's not normal for this to happen. We have a Dynamic threshold setup, but because the CPU spikes from 0 to 100 very quickly, LM doesn't seem to like this. If we change the Band numbers to 3 or 4, then it just blankets everything from 1-100 in the band and we'd never get any alerts on anything. As you can see here, The band doesn't start to "grow" until after the CPU spikes for the first time, then it goes up and continues to go up after the CPU has come back down. Then the next time it spikes, the band grows again. As you can see by the Purple arror, the band was coming down, but then the CPU spiked again, but the band didn't grow in time so we got an alert. Maybe this example is not a good place to try to use Dynamic thresholds. Would we be better off to just set a Static threshold to alert with the normal numbers, but limit it from 17:00 - 5:00 so it only alerts overnight?
