| commit | 0dbc7a434345fa318ee129eaa5cf83681de4936b | [log] [tgz] |
|---|---|---|
| author | Bookatz <bookatz@google.com> | Fri Mar 30 16:21:17 2018 -0700 |
| committer | Bookatz <bookatz@google.com> | Fri Mar 30 16:21:17 2018 -0700 |
| tree | 648209a4dc79c5ea9f9af1729596d8f48b59c868 | |
| parent | f50e78d8f790cd1bb5a6cc37dcdad7815857e471 [diff] |
Statsd MAX now obeys refractory periods too The logic of where refractory period enforcement was moved out of the anomaly tracker and into the metric's predictAnomalyTimestamp. It was done for ORING, but not for MAX. This fixes MAX. Bug: 74446029 Test: adb sync data && adb shell data/nativetest64/statsd_test/statsd_test Change-Id: I51e43c7c132f424af8fe20a37f2ad10cc55b5989