summaryrefslogtreecommitdiff
path: root/apex/statsd/framework/java/android/app/StatsManager.java
Commit message (Collapse)AuthorAgeFilesLines
* Migrate apex/statsd -> packages/modules/StatsD/apexBaligh Uddin2020-12-041-725/+0
| | | | | | BUG: 167962588 TEST: TH Change-Id: Ifbf8f6310031254f5a53b382cfa7d44e9d3b7bf0
* Tighten up Binder.clearCallingIdentity() usage.Jeff Sharkey2020-10-061-1/+1
| | | | | | | | | | | | | | | | | | | | The recently added AndroidFrameworkBinderIdentity Error Prone checker examines code to ensure that any cleared identities are restored to avoid obscure security vulnerabilities. This change is a purely mechanical refactoring that adds the "final" keyword to the cleared identity to ensure that it's not accidentally modified before eventually being cleared. Here's the exact command used to generate this CL: $ find . -name "*.java" -exec sed -Ei \ 's/ (long \w+ = .+?clearCallingIdentity)/ final \1/' \ {} \; Bug: 155703208 Test: make Exempt-From-Owner-Approval: trivial refactoring Change-Id: I832c9d70c3dfcd8d669cf71939d97837becc973a
* Merge "Retry pullfinish with empty payload if call fails" into rvc-devTej Singh2020-06-011-1/+9
|\
| * Retry pullfinish with empty payload if call failsTej Singh2020-05-291-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | If the first call for pullFinished fails, it is likely because the transaction is too large. Currently, if this happens statsd will just sleep until the timeout. With this change, the client will retry calling pullFinish if the first attempt fails, but with an empty payload (and with success = false) to cause the puller to fail fast, and so statsd does not wait for the timeout. Test: atest GtsStatsdHostTestCases Bug: 157768117 Change-Id: I1af29b6c83039ab56ef847832a600d4afea34000
* | Decrease default pull timeout to 2 seconds.Tej Singh2020-05-291-1/+1
|/ | | | | | | | | | | This can result in more pull failures, but can prohibit slow pullers from slowing down statsd. Test: atest GtsStatsdHostTestCases Test: atest statsd_test Test: atest FrameworkStatsdTest Bug: 154056912 Change-Id: Ie30bd3584d808bb11aaaf0fe2057c9adfb198644
* Fix statsd NPE on setPullAtomCallbackTej Singh2020-05-051-4/+0
| | | | | | | | | | | | | | | | Suspected root cause: if a process crashes right after calling setPullAtomCallback, it's possible that oneway binder calls can queue but do not execute before the process crashes. Then, when the process crashes, nothing has a strong reference to the IPullAtomCallback, so it gets deallocated. Then, when the oneway call actually executes, the callback is null. This is being followed up in b/155793159 Regardless, statsd should handle null input properly. Test: GTS test in ag/11348719 now passes Test: atest GtsStatsdHostTestCases Bug: 153822941 Change-Id: Ic6d415e10eca8d133290de80cb61e1634590ca6a
* Merge "Remove Exception in getRegisteredExperimentIds" into rvc-devJeffrey Huang2020-04-011-4/+0
|\
| * Remove Exception in getRegisteredExperimentIdsJeffrey Huang2020-03-311-4/+0
| | | | | | | | | | | | | | | | | | | | | | This check was not useful since service can only be null if system server is not running or the app does not have permissions to access statsd. This check is not done anywhere else, so removing it for consistency. Bug: 150645647 Test: atest StatsdHostTestCases Change-Id: I6465697f0157c5a9583025979c55cb2e3dc1ef84
* | Guardrail for pull cooldown/timeoutTej Singh2020-03-301-2/+3
|/ | | | | | | | | | | Enforce a 1 second minimum cooldown and a 10 second maximum timeout on pullers. Test: bit statsd_test:* Test: atest LibStatsPullTests Test: atest GtsStatsdHostTestCases Bug: 152543610 Change-Id: Ida0047235a7e56d7b700f1a7ab5cfbc2a147caeb
* Address Puller API FeedbackTej Singh2020-03-051-40/+42
| | | | | | | | | | | | | | | | | | | | 1. Rename registerPullAtomCallback to setPullAtomCallback 2. Rename unregisterPullAtomCallback to clearPullAtomCallback 3. Add getters to PullAtomMetadata 4. Change Ns to Millis (when I tried to make it Nanos, I received a built time error saying to prefer millis unless we need the precision. We do not need the precision, so I changed it). 5. Fix out of order params. I did not change usePooledBuffer to setPooledBuffer because I think use is more appropriate for our use case. Test: make Test: atest PullAtomMetadataTest Test: atest GtsStatsdHostTestCases Bug: 149475498 Change-Id: Ib07aa57a6e02c77917fe0e65a3d4a77c00ce8565
* Catch IllegalStateException in StatsManagerJeffrey Huang2020-02-201-0/+15
| | | | | | | | | StatsManagerService throws IllegalStateException when statsd is not available. This causes GMSCore to crash. Bug: 149914783 Test: Manual, verify play store no longer crashes Change-Id: I45cd679600ccfdb7977ecfd4437b62f56034fed2
* Remove more Slog usages in statsd apexMuhammad Qureshi2020-02-091-10/+10
| | | | | | | | Slog.* --> Log.* Bug: 149128236 Test: m Change-Id: I926f292dd5562af132774670c35fe2ca4e853bf8
* Create REGISTER_STATS_PULL_ATOM permissionMuhammad Qureshi2020-02-051-2/+4
| | | | | | | | | | Create a permission to allow clients to register pull atom callbacks to statsd. This permission should allow mainline modules and other platform clients register puller callbacks, but is not intended for 3p apps. Bug: 146462168 Test: atest CtsPermission2TestCases Change-Id: Iea50d137e2cc9f34644c8aa9548a7445f5ec16b8
* Cleanup StatsPullAtomServiceJeffrey Huang2020-01-271-20/+0
| | | | | | | | | | Move all variable declarations to top of file Delete unused puller registrations Migrate to new API Test: m -j Bug: 145565211 Change-Id: I03890e333dd179be3b8d075657cf84a2247a473c
* Migrate away from using ServiceManagerJeffrey Huang2020-01-231-2/+5
| | | | | | | | | Create a wrapper class to access binder objects published by statsd mainline module Bug: 147923515 Test: atest com.google.android.statsd.gts.StatsdHostTestCases Change-Id: I9ea3677d88c790c856e4e89318ae2ce67ac7df1e
* Migrate StatsManager to apexJeffrey Huang2020-01-231-0/+722
Link frameworks-statsd.jar against framework-all since it is currently infeasible to to link against stubs Linking against stubs in frameworks/base cannot be done because we still have StatsLog that calls StatsEvent.getBytes which is a hidden API. We can't move StatsLog to the apex because of hidden APIs in the autogenerated code which is currently being migrated. Test: m -j Bug: 147923515 Change-Id: I0a59dce83a8075bdde3e72d1d8eceef2ed572791
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-12 07:11:00 +0000