| a4e616e0dc5d1497bec3d4197dbdd89d21a4deda |
|
30-Jul-2016 |
Jack Yu <jackyu@google.com> |
Merge "Added todo items for a potential metrics issue" into nyc-mr1-dev
|
| dc5a63bdd153f32d68962bc8271079295b41e1ee |
|
30-Jul-2016 |
Jack Yu <jackyu@google.com> |
Added todo items for a potential metrics issue
bug: 29390529
Change-Id: I15826d5f513748a423eb4cc103f1b010ddad2126
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|
| 90cbc5b44450e9806ce0227d125fe7d5107c7c4b |
|
29-Jul-2016 |
Hugo Benichi <hugobenichi@google.com> |
Fix missing IpConnectivity metrics
The IpConnectivityLog class looks up MetricsLoggerService once only
at creation. If a IpConnectivityLog user instantiates this class too
early during the boot process, the MetricsLoggerService is not found
and no event can be recorded.
This patch makes IpConnectivityLog attempt to look up
MetricsLoggerService as long as it hasn't found it yet.
This allows IpManager and ConnectivityService to upload
android.net.metrics events.
Bug: 30490301
Change-Id: I97102b95a775ea9e90351b9887ae4661fddc2af9
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|
| 3bba249c4711b10b2ba5335c7b6653dc570aae64 |
|
30-May-2016 |
Hugo Benichi <hugobenichi@google.com> |
Tests for IpConnectivityMetricsLog
Bug: 28204408
Bug: 29035129
Change-Id: I429562a00904188947b11da9928ec5c01296ff97
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|
| 623ab7d7a6a7d948fa6338a3992b2680d0192427 |
|
30-May-2016 |
Hugo Benichi <hugobenichi@google.com> |
ConnectivityMetricsLogger subclass for IpConnectivity
IpConnectivityEvent was using ConnectivityMetricsLogger directly for
logging events. However ConnectivityMetricsLogger keeps track in a
thread-unsafe way of skipped events rejected by MetricsLoggerService.
This patch introduces a subclass of ConnectivityMetricsLogger that
does not track skipped events, for using in IpConnectivityEvent.
It also qualifies the mServiceBlockedTimestampMillis variable as
volatile so that throttling is effective accross concurrent callers
of logEvent.
Bug: 28204408
Bug: 29023888
Change-Id: I33707ba1d07487b42f3ce9a1ad9a66d785e99fa7
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|
| c2c39e28f3ae7f993821dda55b69605989967f60 |
|
19-Apr-2016 |
Pavel Zhamaitsiak <pavelz@google.com> |
Add wrappers for IConnectivityMetricsLogger functions
Bug: 25691077
Change-Id: I51fa34a4815fb04e33d3b02f0134e3555afc3900
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|
| f6f24c03f39016ee927e8bdbcff75a53841829c8 |
|
15-Apr-2016 |
Pavel Zhamaitsiak <pavelz@google.com> |
Make ConnectivityMetricsLogger and related classes @SystemApi
Bug: 25691077
Change-Id: Ia98d0a52a9541d9ae773be2b0e962d609f9dd7ee
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|
| d1cb256b3efd2c00f1c44541b5589c2ea17b3cb8 |
|
01-Apr-2016 |
Pavel Zhamaitsiak <pavelz@google.com> |
ConnectivityMetricsLogger: Switch to "pull" model
If subscriber is in external app, its process can be killed. This would
lead to loss of events. To avoid that, we will be storing events in the
logger service. Clients can periodically pull data from it.
Another option for client apps is to register PendingIntent which will be
sent when certain number of new events has been received.
If events are logged at unexpectedly high rate from particular component,
then throttling mechanism will activate and new events will be blocked for
some time from that component.
Change-Id: I710409626eb5a42bcd3fe8126eac6b756fa1ab8b
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|
| 02b3e6bfc5bbd5f1a8ce1ce68976e59142073b6f |
|
03-Feb-2016 |
Pavel Zhamaitsiak <pavelz@google.com> |
Add Connectivity Metrics Logger service
This service can be used to pass events to metrics collection service
Change-Id: I213874300693cd121f2c8676f70893315de4c4c0
/frameworks/base/core/java/android/net/ConnectivityMetricsLogger.java
|