342
edits
TestEngineering/Performance/FAQ: Difference between revisions
→Duplicate / new alerts
Alexandrui (talk | contribs) |
Alexandrui (talk | contribs) |
||
| Line 209: | Line 209: | ||
Yes, we can. We have other projects and a [https://wiki.mozilla.org/images/c/c0/Larres-thesis.pdf masters thesis] has been written on this subject. The reality is we will still need future data points to show a trend and depending on the source of data we will need to use different algorithms to analyze it. | Yes, we can. We have other projects and a [https://wiki.mozilla.org/images/c/c0/Larres-thesis.pdf masters thesis] has been written on this subject. The reality is we will still need future data points to show a trend and depending on the source of data we will need to use different algorithms to analyze it. | ||
== | == How can duplicate alerts can be identified? == | ||
One problem with [[TestEngineering/Performance/Sheriffing/Tree_FAQ#What_is_coalescing|coalescing]] is that we sometimes generate an original alert on a range of changes, then when we fill in the data (backfilling/retriggering) we generate new alerts. This causes confusion while looking at the alerts. | One problem with [[TestEngineering/Performance/Sheriffing/Tree_FAQ#What_is_coalescing|coalescing]] is that we sometimes generate an original alert on a range of changes, then when we fill in the data (backfilling/retriggering) we generate new alerts. This causes confusion while looking at the alerts. | ||