diff options
| author | 2022-08-09 16:39:07 -0700 | |
|---|---|---|
| committer | 2022-10-06 04:33:17 +0000 | |
| commit | 4c5b296cb12ba7cd60b7a78a21be2934b94b8b86 (patch) | |
| tree | db1f0db5075930881c52f0191c1acc1f7108e88b /services/coverage/java | |
| parent | eec01732751bfc8b8caac4bb8a2869bf48b480d8 (diff) | |
Logging second order reasons for process starts
Currently the reason is described as the hosting type and name
of the lifecycle component that is being started. Adding a field to
describe the trigger that led to the component being invoked.
Starting with logging when an alarm caused a broadcast to start in the
app. Other examples of triggers that can be added are jobs for services,
push-messages for broadcasts, etc.
Test: make statsd_testdrive
statsd_testdrive 169
Bug: 242928495
Change-Id: Iffa03bd99f9ef6907444b3e3204d2a2f13e28102
Merged-In: Iffa03bd99f9ef6907444b3e3204d2a2f13e28102
(cherry picked from commit 64d4919530e55f508e3a146fc7eaa13a2fa8e4f5)
Merged-In: Iffa03bd99f9ef6907444b3e3204d2a2f13e28102
Diffstat (limited to 'services/coverage/java')
0 files changed, 0 insertions, 0 deletions