Modifies statsd_testdrive to allow up to 100 atoms to be pulled at a
time. Uses trigger event with app breadcrumb so that the puller happens
once.
Bug: 128893770
Test: statsd_testdrive 10021 (temperature)
Change-Id: I185a7eb1b32a6b19596601dcf5a1ba7a633e4e35
NetworkDnsEventReported -The message represents the entire lookup operation,
which may result one or more queries to the recursive DNS resolvers.
DnsCallReported - Those DNS queries are individually logged in DnsCallReported
to enable computing error rates and network latency and timeouts broken up by
query type, transport, network interface, etc
Test: make statsd_testdrive
./out/host/linux-x86/bin/statsd_testdrive 116 => pass
Bug: 129253665
Change-Id: Ib75affea5d849437a293affbe294732153511d97
Merged-In: Ib75affea5d849437a293affbe294732153511d97
In Q, mainline modules will can add atoms after the platform ships.
Statsdstats now supports atom counts of up to 100 atoms that are added
after Q ships. Note: pixel/oem pushed atoms will also get counted now.
Also fixes a typo in prepareFirstBucket
Bug: 131448746
Bug: 128363379
Test: statsd_test
Change-Id: I149c91136fb7649f0c9a0d6e83bc20f8461e45e2
This allows setting one metric with both IMMEDIATE and ACTIVATE_ON_BOOT
EventActivations
Also, if an on-boot Activation that is already active gets another
activation signal, ignore it.
Bug: 128880263
Fixes: 128880263
Test: statsd_test
Change-Id: I8d483882836c9abc184230b4a70d4734d49d93c3
Update the experiment id logic for binary push and train info to reflect
the new design.
Bug: 131267440
Test: gts tests added in topic
Test: gts-tradefed run gts-dev --module GtsStatsdHostTestCases
Change-Id: I09ff331c9d4b91c2e13a51b832c33d11b34ec0d7
define atoms/messages that express the media.metrics events as they get
passed to statsd. This mirrors the data that was already being
collected via 'dumpsys media.metrics'.
Update the test app's list of acceptable uid's from which it takes
submissions to include the media.metrics service.
Bug: 118782504
Test: statsd/test_drive
Change-Id: I825f6cb7a9baa61f51c45b1b56a20dd94ae48015
Statsd is pulling data when the metric is not active. This cl causes
statsd to skip data pulls when the metric is not active
Test: unit tests
Test: cts
Bug: 129910938
Change-Id: Ibc9459f38c2f6128b8a1f10c6dea683bfe07b22a
condition_true_nanos is only written to proto when there is a condition.
Bug: 130831927
Test: statsd_test
Change-Id: I059ca478879567757658bce51d6a751f844a33f6
Remove the guardrail/MemoryLeakTrackUtil.* files. They aren't used
and they are a copy of frameworks/av/media/utils/MemoryLeakTrackUtil.*.
Bug: 130028357
Test: Enable backtrace for calendar, run am dumpheap -n <PID> <FILE>
Change-Id: I6ce69465b0c04fae97b3622df2763a2996063d85
Merged-In: I6ce69465b0c04fae97b3622df2763a2996063d85
(cherry picked from commit 98180a344cfd08748dcf5a6aa5aebfdeb7e78b62)
Pull value of VmSwap from /proc/PID/status when capturing
ProcessMemoryState atom.
Before change:
(average pull time nanos) 43355896
(max pull time nanos) 75649278
After change:
(average pull time nanos) 86307073
(max pull time nanos) 151681474
Delta: 2x increase
Pulling frequency is controled via statsd and we trade-off more
expensive reads for more actionable data (helping detect memory leaks).
Bug: 130624561
Test: atest MemoryStatUtilTest
Test: benchmark pulling ProcessMemoryState atom
Test: manually take a statsd report
Change-Id: I1d90563b70b5253b3d31ddab4810db870620c4d4
(cherry picked from commit 65a9b7122ada9db7a95cdfe31fa97b328bd04a06)
Adds a ThermalThrottlingSeverityStateChanged atom to replace
ThermalThrottlingStateChanged. The new atom logs per severity level and
temperature type/name.
Test: print-logs and testdrive while injecting a high temperature via
emul_temp
Bug: 119688911
Change-Id: I2fbcae36eec96bd2c484e0d85ca1617f802a79d9
Intelligence is a mainline module with several counter usecases.
Rather than create a very similar atom for each we'll use an event enum
for these simple counters.
Test: compile proto
Bug: 129491708
Change-Id: Ic30c0d6e15f6afbef90d89d1b53a20f8af38902e
Usually after config owner calls statsd to get data, statsd will remove that data
forever. This cl adds an option to save historical data locally so that when a bugreport
is taken, it contains historical statsd metrics for debugging.
+ All existing guardrail on storage still apply, and local history data has lower
priority when the guardrail is hit. On top of that, statsd will remove history
files that are more than 2 days old.
+ Also fixed issues inside StorageManager (e.g.,
using string::compare to sort by timestamp is problematic, redundant file size read, etc)
Test: statsd_test and manually
Fix: 126562025
Change-Id: I5238b9fd3069cbef5bcccabd2212bc4d6c734702
