Professor
ProfessorWe have used both together. For something like CPU Utilization, I would have the dynamic threshold ignore the bottom band. Generally you don't care if something is using "less" in this case (sometimes you do care tho of course).
We then have our static threshold set, but have it a little higher then we normally would. That way if the utilization slowly creeps up, it will still trigger an alarm after a bit.
ProfessorYes, we don't care about anything below the band, just above. The issue I have is that every weekday, at 5AM, the CPU spikes up to 100%. We know it's going to happen. Since it happens every weekday, if LM really "Learned" what was normal for a server, it should put that gray area at 100% right at 5AM. According to the screenshot above, that's not happening. It's waiting for the CPU to spike up and is then moving the bar up to compensate. That doesn't help us because this isn't a gradual increase. It's 0% one minute and 99% the next.
We thought the whole point of Dynamic is they are supposed to look at the server and learn it's behavior over time. This doesn't seem to actually work or something is wrong.
