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/src/metrics/ValueMetricProducer.cpp
|
47234644caf0f2a1aac3a1db8c548b1a25b1cfe2 |
|
14-May-2018 |
Chenjie Yu <cjyu@google.com> |
Configurable data error action in value metric Right now in value metric, if a later pull produces a smaller number than the previous one, we use absolute value of the current value. This is not correct for some atoms as listed in the CL, which should just take 0. For some other atoms, this is unexpected error and should just dump stale data. Test: manual test Bug: 79265262 Change-Id: I59fbfd96cbb57be22cd8d21cb57a7c60ca6856ee
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
613a7e2a7dc7f7e9f215390fd5138187c7d17b3c |
|
09-May-2018 |
Yangster <yanglu@google.com> |
Should not use the absolute value when the value does not change. Test: statsd test BUG: b/79265262 Change-Id: Ic654e1a07a505ec0e073a41fb41bcd38a29b125e
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
b85e5616dfa153eea1e61e99427164c5102dbbd3 |
|
02-May-2018 |
android-build-team Robot <android-build-team-robot@google.com> |
Merge "Reduce statsd log data size." into pi-dev
|
9def8e3995b1034d943a0fd22b6e512bfacdab77 |
|
17-Apr-2018 |
Yangster-mac <yanglu@google.com> |
Reduce statsd log data size. 1. Hash the strings in metric dimensions. 2. Optimize the timestamp encoding in bucket. Use bucket num for full bucket and millis for partial bucket. 3. Encode the dimension path per metric and avoid deduping it across dimensons. Test: statsd test Change-Id: I18f69654de85edb21a9c835c73edead756295e05 BUG: b/77813755
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
a802d73da625ac72f6a0211aab017f365139112d |
|
24-Apr-2018 |
Yangster-mac <yanglu@google.com> |
Clear the past buckets for no-report metrics Test: statsd tests. BUG: b/78503732 Change-Id: I3de855929ad05677769cffaae4fea2db0d2f32da
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
81245fd53a0bd627fa87e3a69dd667c7d6696ede |
|
12-Apr-2018 |
David Chen <dwchen@google.com> |
Adds option to drop small buckets for statsd. We notice that some of the pulled metrics have a ton of data, and during app upgrades, we're forming partial buckets that represent small periods of time but require many bytes of data. We now have an option to drop these buckets that are too short. Note that we still have to pull the data to keep the metrics for the next bucket correct. We include a new field in the value and gauge metric outputs so that it's easy to tell when a bucket was dropped. We drop the partial buckets also from anomaly detection since we should be computing anomalies from the same data that is reported. Test: Added unit-tests for value and gauge metrics. Bug: 77925710 Change-Id: Ic370496377c6afd380e02278a6c1ed8b521a2731
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
e68f3a5811209eeab71976bc583c6075d9a5979a |
|
04-Apr-2018 |
Yangster-mac <yanglu@google.com> |
Flush the partial bucket when startd shuts down or config updated. Test: statsd test BUG: b/77556036 Change-Id: Ie4a04ace55e07c4529cdff5906ba874f8815f620
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
d9afdee26f01d1e0277749959094d9f396799a69 |
|
27-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Support sliced condition change in GaugeMetric" into pi-dev
|
427d372552490a2c5ac4041fe345b15f69451f57 |
|
22-Mar-2018 |
Yao Chen <yaochen@google.com> |
Support sliced condition change in GaugeMetric TODO: We need CTS to verify the behavior. Bug: 73958484 Test: statsd_test Change-Id: I56406983ddede12bc6a2e12188693a0c51ccae5c
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
c58750578fdf6e54500e9deabe7d5062afbd6e09 |
|
09-Mar-2018 |
Chenjie Yu <cjyu@google.com> |
Up the dimension key limit for CpuTimePerUidFreq This atom logs time spent on cpu per frequency per uid. On marlin, there are 27 frequency steps per uid (should be 50+ if flatten to both cores) On walleye, there are 52 frequency steps per uid. So it easily goes to 6k data. Soft limit set to 6k now. Hard limit set to 10k to accommodate future processors Memory impact: on marlin, start memory no config is 2,346K after using this atom in one guage metric, it is 3,067K Bug: 72505991 Test: cts test Change-Id: I067a32e54e4a457fdf9a25911aa16030e893ef4d
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
aaadf6663fdc8787947d67bc14841d20094bd072 |
|
14-Mar-2018 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Statsd: Remove storage of bucketNum" into pi-dev
|
a78d00874d4e274937734a1b73aef4b6389eb3cd |
|
12-Mar-2018 |
Yangster-mac <yanglu@google.com> |
Dump the stats for count/gauge/value metrics. Bug: b/74159560 Test: statsd test Change-Id: I1410309ecfdfc2a5becf8d0c620c68a621ebc5fa
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
3f5ab3ff1d66e53c26e3a5951dc0804bca5467a8 |
|
13-Mar-2018 |
Bookatz <bookatz@google.com> |
Statsd: Remove storage of bucketNum Past buckets had a field mBucketNum, storing the "bucket number" they represented. Currently, the concept of bucket number is used by Anomaly Detection (although this may not be necessary), but these stored values are not used at all, so removing them will save RAM. Test: statsd tests still pass Bug: 74607818 Change-Id: Iacc343bc39c5035f6e2f236c03de1d91606eff4c
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
13fb7e4eeaf7aee408821afe7ee55a5167e49e59 |
|
08-Mar-2018 |
Yangster <yanglu@google.com> |
Statsd cpu optimizaton - cache the changed dimensions in condition tracker. - avoid query condition wizard when unnecessary. - avoid copy dimension keys in condition key generation. Test: statsd tests. BUG: b/73959649 Change-Id: I17d68e2a82643de3f421309841e75f84c6fd8f43
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
5ee0787024cc446a21008ff5710dec19c6afc834 |
|
06-Mar-2018 |
Yi Jin <jinyithu@google.com> |
Use uint64_t instead of long long as API type for consistent reason. Bug: 74118023 Test: manual Change-Id: Icd5f506c76d3a008a79cb6c9d2061962ca7fdd40
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
06dba5d79c096b02d3ba6fb73e64451ff12e388d |
|
26-Jan-2018 |
Yao Chen <yaochen@google.com> |
Add API to let metrics directly drop data without writing to an output. + Metrics will do flushIfNeeded() to correctly move the clock and informing AnomalyTracker the past bucket info, and then clear past buckets. + We will still keep the current bucket data for the validity of the future metrics. Bug: 70571383 Test: statsd_test Change-Id: Ib13c45574974e7b4e82bd8f305091dc93bda76f5
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
8a8d16ceea1e5b7a2f8c41e17b5d993035f50f5d |
|
08-Feb-2018 |
Yao Chen <yaochen@google.com> |
Statsd CPU optimization. The key change is to revamp how we parse/store/match a log event, especially how we match repeated field and attribution nodes, and how we construct dimensions and compare them. + We use a integer to encode the field of a log element. And also encode the FieldMatcher into an integer and a bit mask. The log matching becomes 2 integer operations. + Dimension is stored as encoded field and value pair. Checking if 2 dimensions are equal is then becoming checking if the underlying integers are equal. The integers are stored contiguously in memory, so it's much faster than previous tree structure. Start review from FieldValue.h Test: statsd_test + new unit tests Bug: 72659059 Change-Id: Iec8daeacdd3f39ab297c10ab9cd7b710a9c42e86
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
16049578001364e1fcb0f10d6f94868081e57316 |
|
02-Feb-2018 |
David Chen <dwchen@google.com> |
Modifies statsd output for start and end times. We include the start of when the last dump occurred and the current timestamp. These timestamps are shared across all metrics, so there's no advantage in duplicating these numbers across all metrics. Also, we should use elapsed realtime instead of times based on wall clock, which can jump around and go backwards. Test: Test that statsd can still build and adb shell cmd stats dump-report doesn't crash. Change-Id: I819e5643cee75dfa3e78a58f94c9d61ededa78d7
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
635b4b37210bd61b73aebf19298e38b8fb382e85 |
|
24-Jan-2018 |
Yangster-mac <yanglu@google.com> |
Do not output empty metric reports. Test: statsd unit test passed. Change-Id: I296edbe621eaea72ad2e1dfe656698302614c0f3
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
0ed268b1ec41003c7ed7fbe3c8cba726e7a1dbde |
|
10-Jan-2018 |
Chenjie Yu <cjyu@google.com> |
similar to the samplers in batterystats, when we do diff, if the value is not monotically increasing, we should take the absolute value as the diff. Test: unit tested Change-Id: Idd8a248b4092b1863eb8e50539f8f14b3ac9af9e
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
468ff04fd4cb43a384a3d4948cccd4438be7202a |
|
17-Jan-2018 |
Yangster-mac <yanglu@google.com> |
Proto change for dimension from condition. Test: all statsd unit tests and cts tests passed. Change-Id: I955143aca7c76e2e22a10d7ba42eb797bd32e147
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
2087716f2bdca90c7c3034d556ac12911bd8018e |
|
23-Dec-2017 |
Yangster-mac <yanglu@google.com> |
1/ Support nested message and repeated fields in statsd. 2/ Filter gauge fields by FieldMatcher. 3/ Wire up wakelock attribution chain. 4/ e2e test: wakelock duration metric with aggregated predicate dimensions. 5/ e2e test: count metric with multiple metric condition links for 2 predicates and 1 non-sliced predicate. Test: statsd unit test passed. Change-Id: I89db31cb068184a54e0a892fad710966d3127bc9
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
d5aa01b3716e07463019fa772f07a40613f9e39e |
|
20-Dec-2017 |
Yao Chen <yaochen@google.com> |
Remove the hacky HashableDimensionKey. + Add a real HashableDimensionKey as a wrapper of the dimension. So we can get rid of the maps that we kept. Pay down technical debt and reduce memory usage. Test: statsd_test & manual Change-Id: I233280cf1e2ce93da6a8cd4e8514abb066f4016d
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
e6abcbed993c81562cddb4122235fc2bcffff8e8 |
|
17-Dec-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Turn off verbose logging, remove the fake config."
|
3c0b95ceb520c6b23871da90c23f89c55b76b560 |
|
16-Dec-2017 |
Yao Chen <yaochen@google.com> |
Turn off verbose logging, remove the fake config. Test: statsd_test & manual Change-Id: I43068c8db006cbbeccacaa9d8426ab4d0394313a
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
f09569f848ca0b81a21a74e9f4dd8bd9a886151a |
|
14-Dec-2017 |
Yao Chen <yaochen@google.com> |
Further reduce statsd memory usage. + Remove the protobuf *Metric object from MetricProducers -- This saves ~150 bytes per metric. + Remove the StatsdConfig from ConfigManager -- This saves us xKB per config. + Also remove alerts from fake config to avoid crash (Bug: 70627390) + Other misc fixes too. Test: statsd_test & manual Change-Id: Ied4eb3fa31c50599817b3a5e1caf5077c487fad2
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
2794da220fa853c109905586a87202eff361c175 |
|
14-Dec-2017 |
Yao Chen <yaochen@google.com> |
Remove dead code in statsd Remove dead code and shared lib. And fix a bug in ValueMetricProducer Test: statsd_test & manual Change-Id: Ie76bfc02e14ae6a0fa9f8933751fd06397de9411
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
288c60001330a5a924a47c0eebd6097ae3ee5d67 |
|
12-Dec-2017 |
Yao Chen <yaochen@google.com> |
Only create ProtoOutputStream when onGetData() is called. The exception is EventMetricProducer. Each EventMetricProducer will still have a ProtoOutputStream Because LogEvent comes as a fixed 4K, it's more memory efficient to have an 8k ProtoOutputStream for storing the events. Also removed finish() api in MetricProducer, which was intended to use with Dropbox. Test: statsd_test & dogfood app Bug: 70393808 Change-Id: I2efe4ecc76a88060a9aa5eb49d1fa6ea60bc5da8
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
6a8c799d901cbd166aa6463d7dea231bcf594a1e |
|
29-Nov-2017 |
Yao Chen <yaochen@google.com> |
Revert "Thread-safe metric producers." This reverts commit 8de6939c494da838f6dbbda0631f66425dbbd25b. Change-Id: Ieae841bfc5339b569f0fca909a6066de72806617
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
8de6939c494da838f6dbbda0631f66425dbbd25b |
|
27-Nov-2017 |
Yangster <yanglu@google.com> |
Thread-safe metric producers. Test: unit test passed Change-Id: Ie47404e8649b63ee8ac32e40189a47f6cb7a9def
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
7c334a129e93e405a72e8299a1cd928af079d14f |
|
22-Nov-2017 |
Yangster <yanglu@google.com> |
Make member function as const whenever possible. Test: unit tests passed. Change-Id: I751cabf305a4b5aa2095853cc951837da0df4c78
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
1ff4f4325882d812ded4f75ee6c2b6d352a85c9e |
|
17-Nov-2017 |
Yao Chen <yaochen@google.com> |
Statsd test app. Features: + Push baseline config to statsd + Have buttons to write events to StatsLog (plug/unplug, screen on/off, wake locks) + Dump stats log report, and display it on screen (currently support DurationMetricData display). Test: manual Change-Id: Ia58d215d30ed7570c0aa1b0627d3b88f8355d425
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.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/src/metrics/ValueMetricProducer.cpp
|
7f8def9d5a71f4ccb1ecdd90637f7b3c162dcab8 |
|
03-Nov-2017 |
Chenjie Yu <cjyu@google.com> |
pull cpu time per freq also adjust lock for ValueMetricProducer.cpp Test: manual test Change-Id: Ib96e3011d7bcf44ac92346d880196c425623a86f
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
b0378b093d9b937fe9a731a601d670d50f263078 |
|
10-Nov-2017 |
yro <yro@google.com> |
1. Add FIELD_COUNT_REPEATED bit masks to repeated fields that were previously missing 2. Resolve segfault when serializing proto into vector of uint8_t 3. Add a local byte size variable for EventMetric data as we cannot call size() of ProtoOutputStream before we finish writing. 4. Replace hardcoded conversion of second to nano second with NS_PER_SEC Test: statsd, statsd_test Change-Id: I47a2ce2b05e6191c18596489682118edcb41e945
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
17adac9cf3e03ad95372eb8657b26909d0414ac0 |
|
09-Nov-2017 |
yro <yro@google.com> |
Finish migrating to use ProtoOutputStream. This change will take the outputs of each MetricProducer's and merge the results into ConfigMetricsReport which holds ConfigKey, repeated field of StatsLogReport, and UidMap. The data will be represented as vector<uint8_t> which can be passed down to binder call for clients to pick up. Also, all unnecessary dependencies to stats_log proto have been removed. Test: statsd, statsd_test Change-Id: Ia69137cbc8613644a892e6be1e87b4858bd39fe3
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
2b0f88678b2877a8e9f83cea60f097322b078367 |
|
06-Nov-2017 |
yro <yro@google.com> |
Migrate all remaining MetricProducers to use ProtoOutputStream Test: statsd, statsd_test Change-Id: I1087e1c1ffb372ca288dfc575cb7a372b11ce8c5
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
93fe3a34a02c673eaee4a2d18565ba8df20685cb |
|
02-Nov-2017 |
Yao Chen <yaochen@google.com> |
Add unit tests for CountMetricProducer, EventMetricProducer And other miscellaneous fixes. + clang-format + 2 bug fixes, one in dump-report command, one in ResourcePowerManagerPuller Test: statsd_test Change-Id: Ibd164d948ad62adcc529d813df1210781e38be47
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
5305e1ddc22bfe9ad941cb2550987aaba8de234c |
|
31-Oct-2017 |
Chenjie Yu <cjyu@google.com> |
pull resource power manager stats into statsd Test: tested on device and check output Change-Id: I65932a5527d6099e12546b6928a24f3616e54e16
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|
b3dda41a5a48ddfa44dc8fa939ab495926a0195d |
|
24-Oct-2017 |
Chenjie Yu <cjyu@google.com> |
reretry ValueMetric implementation and pulling mechanism Note: This is for value metric. The default operations is sum the diffs. The test uses kernel wake lock, which also needs dimension by kernel wake lock name. The test is a bit cumbersome as it needs StatsCompanionService to do the alarm, which is not exact alarm. The internal state of a slice of bucket would look something like this: 4:ipc0000005e_727_android.hardwar 0 0 4:SensorService_wakelock 40 64 4:ipc0000005c_727_android.hardwar ... Test: manual test on device. Change-Id: I2ed0ac7d3c5fcba8b7611d46f38a38ffd8bdc92a
/frameworks/base/cmds/statsd/src/metrics/ValueMetricProducer.cpp
|