summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramStore.java
diff options
context:
space:
mode:
authorTianjie Xu <xunchang@google.com>2019-07-22 14:25:14 -0700
committerTianjie Xu <xunchang@google.com>2020-01-17 00:26:01 +0000
commit5d8df1f08c5f2f8aa023e3fa4714c880a11e79c8 (patch)
tree4a1438755e517b5170200ce601575124dba9cf79 /rs/java/android/renderscript/ProgramStore.java
parent8da97bddbd1a7b07e4bf2e5cf58ac1373a271fb8 (diff)
Adding atoms for metrics logging
Define the atom protos for UpdateEngineUpdateAttemptReported UpdateEngineSuccessfulUpdateReported The fields for both atoms are copied from the already reported Tron counters, except for the source fingerprint. By defining our own proto, we can have a better insight about each update events. It also makes the query easier without the server side work to correlate each counters. Sample output from testdrive shows: data { elapsed_timestamp_nanos: 64932607816092 atom { update_engine_update_attempt_reported { attempt_number: 1 payload_type: FULL duration_boottime_in_minutes: 0 duration_monotonic_in_minutes: 0 payload_size_mib: 510 attempt_result: METADATA_VERIFICATION_FAILED error_code: DOWNLOAD_METADATA_SIGNATURE_MISMATCH fingerprint: "google/walleye/walleye:R/MASTER/eng.xuncha.20190731.151212:userdebug/dev-keys" } } } Bug: 138253582 Bug: 137682371 Test: run statsd_testdrive and check events Merged-In: Ic502acc8831fe4da0b32a826171d10e9c0f9876d (cherry picked from commit 167c3db93401adccc703815a9d71ef057b17e780) Change-Id: Ifa57f23135b4cd63888df2b8f25650be133bb1de (cherry picked from commit f00d7fb3bd217bf236adb936febdb44e59250c78)
Diffstat (limited to 'rs/java/android/renderscript/ProgramStore.java')
0 files changed, 0 insertions, 0 deletions