Closed Bill-Kunj closed 1 year ago
A) There were 2 CPU percentage tests, I deleted the 1st one that we did not label which was called "Panel Title." B) For the CPU percentage test I changed the evaluation interval from 10 seconds to 1 minute. The evaluation interval of 10s was too aggressive, it was good for testing the alert but not so good to keep as a final standard setting.
I think there's a floating point precision issue somewhere. We may need to round our percentages to two or three digits in order to avoid false alarms @Strecoza33 @azazime
@DPMBarnes and @azazime believe this is fixed.
Might need reopening but believed fixed.
Discord alert shows
>100%
CPU usage on devnet, so there may be something wrong in the metric calculation