021e25307d815452ceee7e189b36c7072b53c1df |
|
16-May-2018 |
Chenjie Yu <cjyu@google.com> |
ValueMetric pushed events should check condition + fix unit test flakiness Bug: 79873404 Change-Id: I15b52a79b18c05603640781e4450e7b62fac24ba Fix: 79873404 Test: unit test
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
092a5a9b85782afc2045087f9f29dfda16070f13 |
|
16-May-2018 |
David Chen <dwchen@google.com> |
Fixes Value metrics in statsd and app upgrades. Pulled value metrics with conditions had a subtle bug that caused us to leave the condition on even if it should've been false. Bug: 79778783 Test: Added unit-test and verified on marlin-eng. Change-Id: I31f34791118319b3471f7a6ea8a024e2d511cfe7
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
15f6bbc24f4d7a3d4481d90a18df33d402ddacba |
|
08-Apr-2018 |
Yangster-mac <yanglu@google.com> |
Flush the bucket when creating the metric producer. Use int64 for value field. E2e test for gauge/value metric. BUG: b/74445671 Test: statsd test. Change-Id: I823a0bade8f89834bdfb9cf48864852a47d7b63b
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
ae63b0af946d921ca20aaf1916b12af593ec0e1d |
|
10-Apr-2018 |
Chenjie Yu <cjyu@google.com> |
Drop value if the bucket is totally tainted Bug: 77870358 Change-Id: Ia96970a3254de08f94b91ad53be2fdb9f4db7eb4 Fix: 77870358 Test: unit test
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
b142cc8add29c8c97f6134d35873d23db666027c |
|
31-Mar-2018 |
Yangster-mac <yanglu@google.com> |
Statsd config TTL Roughly check the config every hour to see whether the ttl expired. If so, read the config from disk and recreate the metric manager. Test: statsd test BUG: b/77274363 Change-Id: I16838afe5bbe966c3a0f638869751f9b59a5a259
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
6d370f40fe011bc45967b8b9be50717ef6172fbd |
|
25-Mar-2018 |
Chenjie Yu <cjyu@google.com> |
Add unit test ValueMetricProducer on boundary Mostly to add test to assure the corner cases are covered. One minor logic change is if two true conditions happen, in the case when following happen: (bucket boundary1) -> (condition false) -> (condition true) -> (pull triggered for the boundary1) Previously we take the latest. Now we skip the late boundary pull. Bug: 76384731 Test: unit test Change-Id: I345c2210a58bf03eb91d65742573073d2668358b
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
1a0a941c20eb746868d0de52e3806f69c74d335f |
|
28-Mar-2018 |
Chenjie Yu <cjyu@google.com> |
Fix StatsCompanionService pull on bucket ends + change StatsPullerManager internal time units to be consistent + use series of alarms for pullers, instead of use setRepeating Bug: 76223345 Bug: 75970648 Test: cts test Change-Id: I9e6ac0ce06541f5ceabd2a8fa444e13d40e36983
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
6bf9825b1575bfc3c62ef0a5129f94b6a776ef66 |
|
14-Mar-2018 |
Bookatz <bookatz@google.com> |
Statsd AnomalyDetection improvements Various fixes and improvements to statsd's anomaly detection. Bug: 74607818 Test: make statsd_test && adb sync data && adb shell data/nativetest64/statsd_test/statsd_test Change-Id: Ia67a8eb6da0ea9293f698949e1565f7f024a7cb9
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
932ececa1674c59a8da9f3e32d2651e781b86fc4 |
|
01-Feb-2018 |
Yangster-mac <yanglu@google.com> |
Alarm: wakes up statsd and notifies the subscribers. Test: manually tested it. Change-Id: Id796a68976aeb1611183023ba4e9c6a8b8c44bb8
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
db15052ae2ea34807644e2e97afa908e43ae59fd |
|
15-Feb-2018 |
Howard Ro <yro@google.com> |
Merge "Add a guardrail to limit minimum bucket duration to be 5 minutes except when configured through adb command"
|
330af58f2b8582b855085655fae553cdfaf44e6c |
|
09-Feb-2018 |
Yangster-mac <yanglu@google.com> |
Use elapsed realtime instead of times based on wall clock, which can jump around and go backwards. Test: statsd unit test passed Change-Id: Ib541df99231e171b3be2a24f75632693e36da90e
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
59cc24dbfda4148c1f5ef4de9c8763caa8672443 |
|
14-Feb-2018 |
yro <yro@google.com> |
Add a guardrail to limit minimum bucket duration to be 5 minutes except when configured through adb command Bug: 73287251 Test: statsd_test Change-Id: Iee51fedbaabb2c1f534a6edef3c564da88ef658b
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
27785a8a4a684c831c18f7189a6fa1b98c3573e6 |
|
20-Jan-2018 |
David Chen <dwchen@google.com> |
Partial buckets on app upgrade and fix duration. Statsd will create partial buckets in all metrics producers when an app is upgraded so that we can separate metrics between different versions of an app. By looking at the uid map changes, we can tell which app versions belong to a bucket; for metrics that are not affected by an app version, we can instead join the buckets together. To simplify the logic, the ends of the full buckets are always aligned to when the metric producers were created. These boundaries are computed on the fly by using the bucket number and the metric producers' start times. We keep the anomaly trackers to only be given full buckets; we buffer the partial buckets within each metric producer. Duration metric's MAX_SPARSE is fixed to be implemented as such. In addition, after further discussion, we find anomaly detection on MAX_SPARSE to be unnecessary, so this functionality is removed. Test: Unit-tests added and modified, passed on marlin-eng. Change-Id: I5ff7a9c7f05c406e9faf400c6a39162970ded102
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
9369446f0b04945d6674550728ae81196d6fb5c2 |
|
23-Jan-2018 |
Yangster-mac <yanglu@google.com> |
Support dimension in condition in metric producers. Test: added e2e tests for count/duration metrics sliced by fields in condition and with/without links. Change-Id: Ie34deba68e6780abdde458be3f0ce5284e76a1a2
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
1bf94382d036fa8d61258205c5f4e18cd53cb61d |
|
04-Jan-2018 |
Bookatz <bookatz@google.com> |
Anomaly detection is per dimension Anomalies are now detected and declared per dimension. This means that declareAnomaly now gets access to the key that is responsible for the anomaly. Moreover, the refractory period is per dimension, not overall. So a second anomaly for the same metric but a different dimension can fire within the first dimension's refractory period. Thus, if app A misbehaves and app B misbehaves shortly thereafter, they will both be detected. Eventually this key will be passed to the subscribers, although this cl doesn't do anything with it. Test: adb shell data/nativetest64/statsd_test/statsd_test Change-Id: Id76856dc44fe9ecf91ac81a423e84f97c81d30ab
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
b814481ad1f8d0e429d799b1571a6272e1a7f6c5 |
|
04-Jan-2018 |
Yangster-mac <yanglu@google.com> |
Use TimeUnit enum to specify the bucket size. Test: all statsd unit test passed Change-Id: I4f6b80ba2f8c984b06e46e6de6df3e546e99a968
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
a7fb12d2d285a3a62f5e8956d1bacfa0e15e9d0f |
|
04-Jan-2018 |
Yangster-mac <yanglu@google.com> |
1/ Use FieldMatcher to specify the value fields in value metric. 2/ rename number_of_buckets as num_buckets 3/ use double for the Alert's threshold Test: statsd unit tests passed. Change-Id: Id1f55f14d3712eddee561681e3cd77343f086c7a
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
94e197cceb2ba7df13ff8de04f60bfeec64015d9 |
|
03-Jan-2018 |
Yangster-mac <yanglu@google.com> |
1/ Change all "name" to id in statsD. 2/ Handle Subscription for alert. 3/ Support no_report_metric Bug: 69522276 Test: all statsd unit tests passed. Change-Id: I851b235f2d149b8602b0cad632d5bf541962f40a
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
857aaa520804d846a050e1eeb85d82977c983666 |
|
20-Dec-2017 |
Bookatz <bookatz@google.com> |
Splits AnomalyTracker into two files Splits out DurationAnomalyTracker-specific functions into their own subclass. Test: the unit tests and CTS tests Change-Id: Id6eb74d232b4a9c3a932d805d1ba3f0ba43a88b1
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
de1b5562c8a6fdad1e9d2f409c7aa35a23181d34 |
|
15-Dec-2017 |
Bookatz <bookatz@google.com> |
Statsd value metric anomaly detection Add anomly detection to Value metric in statsd. Test: make statsd_test && adb sync data && adb shell data/nativetest64/statsd_test/statsd_test Test: run cts-dev -m CtsStatsdHostTestCases -t android.cts.statsd.HostAtomTests#testValueAnomalyDetection Fixes: 70240042 Change-Id: I05cf36495cdfd0ac7aa1a922f0e253a60fda1787
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
a7259abde4e89fd91404b14b4845113cd313d1ec |
|
10-Dec-2017 |
Chenjie Yu <cjyu@google.com> |
use running sum for ValueMetricProducer bucket simplify ValueMetricProducer logic for pulled data Test: unit test Change-Id: Ic0a21a543166cc5c34c1fa505dba08d1fc2f510a
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
f2bee6fec965fd42ab223f1a3aa705f07ba79aea |
|
29-Nov-2017 |
Yangster <yanglu@google.com> |
1/ Only expose thread-safe interfaces in metric producer. 2/ Simplify lock logic. 3/ Add test for duration metric producer. Test: all unit test passsed. Change-Id: If6ee2e69a17f12406f4b3ea3553b14642cd636d6
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
b356151e63140085cb96fa16804ee18b3862a4fc |
|
22-Nov-2017 |
Yao Chen <yaochen@google.com> |
Add StatsdStats and guardrail. + StatsdStats is the global class that tracks the stats about statsd. + Added guardrail for classes that have a map which could potentially grow unboundedly with the number of logs. TODO: add unit tests & CTS for StatsdStats, and guardrail add stats for pulled atoms. Test: statsd_test Change-Id: I0ea562de4dd3f6162f7923a9c193420b482c1d51
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
e2cd6d509b17894b95d14523ae3e7c4c7a9a74e3 |
|
10-Nov-2017 |
Yangster-mac <yanglu@google.com> |
1/ Duration anomaly tracker with alarm. 2/ Init anomaly from config based on the public language. 3/ Unit tests for anomaly detection in count/gauge producer. 4/ Revisit the duration tracker logic. Test: unit test passed. Change-Id: I2423c0e0f05b1e37626954de9e749303423963f2
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
80235403d2a80eee1c23dbe856d18194b1b93843 |
|
14-Nov-2017 |
Yao Chen <yaochen@google.com> |
statsd: parse the new format of stats log + Changed how we construct LogEvent, now it's based on the context from log_msg without making a copy of the list. + All stats logs now have the same event tag, the atom id is the first elem in the log. Test: statsd_test Change-Id: I4419380f2ee1c2b2155d427b9f2adb78883b337f
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
d1815dc7b82f99259f6c41cfacc44972b867ef2d |
|
14-Nov-2017 |
Yangster-mac <yanglu@google.com> |
Sync statsd to the public proto changes: 1/ use string id/name for all metrics/configs/matchers. 2/ move alerts out of metric proto. Test: unit test passed. Change-Id: I08269f47be30f83f6dbadf873e7d62213449932b
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|
6736c893a73c567d3794d88ae0d17abab34b7a6f |
|
09-Nov-2017 |
Chenjie Yu <cjyu@google.com> |
Unit tests for ValueMetricProducer StatsPullerManager is refactored so that we can mock it. It may need more refactor pass to make is safer for longer runs. Test: unit test Change-Id: Ief0c99710e4d06e1454678f8b749c9599467d114
/frameworks/base/cmds/statsd/tests/metrics/ValueMetricProducer_test.cpp
|