We've been using analytics to capture load times and other information about our website for about a year now. We've noticed that we occasionally see large spikes in the 'Average' trend line as reported by Telerik. After some analysis, we've realized that the days with these large spikes are directly related to excessively large timings. For example, we might have 1000 timings for a particular day, 999 of them are between 1 second and 30 seconds, and then the remaining one reports a time of an hour and forty three minutes.
Our database would fail after five minutes, so I don't believe it's a valid timing; but I also realize that these numbers are being captured via client-side JS and there are some potential issues.
The problem that I'm having is that, once captured, it destroys the average for the day. We average ~2.5 seconds on most days, but then will have a day with a 9 second average; but by altering the ranges and viewing the data different ways, I'm able to see that it is only one timing that took well over an hour, that is skewing it. Even if create a range that is > 30 - Max and uncheck it; while it does correct the reported average, it does not change the appearance of the average line.
* Is there any recommended way we can ignore timings greater than some value?