summaryrefslogtreecommitdiff
path: root/proto/src
diff options
context:
space:
mode:
authorAhmed ElArabawy <arabawy@google.com>2019-04-01 22:57:54 +0000
committerAndroid (Google) Code Review <android-gerrit@google.com>2019-04-01 22:57:54 +0000
commit5b54cbd6310ebfaf57890d5132576cafa87da785 (patch)
treed012251664281c5892e90a56d891e97342a75485 /proto/src
parent14f221742c7989d9ac0f7fb168e3104fbebea3b5 (diff)
parent048e148ea07a4c57d71a44041be8ff3377f3d09f (diff)
Merge "wifi.proto: Add WifiLock statistics"
Diffstat (limited to 'proto/src')
-rw-r--r--proto/src/wifi.proto30
1 files changed, 30 insertions, 0 deletions
diff --git a/proto/src/wifi.proto b/proto/src/wifi.proto
index af77df60638a..2e58ac2f7cba 100644
--- a/proto/src/wifi.proto
+++ b/proto/src/wifi.proto
@@ -533,6 +533,9 @@ message WifiLog {
// Network Suggestion API surface metrics.
optional WifiNetworkSuggestionApiLog wifi_network_suggestion_api_log = 142;
+
+ // WifiLock statistics
+ optional WifiLockStats wifi_lock_stats = 143;
}
// Information that gets logged for every WiFi connection.
@@ -2461,3 +2464,30 @@ message WifiNetworkSuggestionApiLog {
// Histogram for size of the network lists provided by various apps on the device.
repeated HistogramBucketInt32 network_list_size_histogram = 4;
}
+
+// WifiLock metrics
+message WifiLockStats {
+ // Amount of time wifi is actively in HIGH_PERF mode (ms)
+ // This means the lock takes effect and the device takes the actions required for this mode
+ optional int64 high_perf_active_time_ms = 1;
+
+ // Amount of time wifi is actively in LOW_LATENCY mode (ms)
+ // This means the lock takes effect and the device takes the actions required for this mode
+ optional int64 low_latency_active_time_ms = 2;
+
+ // Histogram of HIGH_PERF lock acquisition duration (seconds)
+ // Note that acquiring the lock does not necessarily mean that device is actively in that mode
+ repeated HistogramBucketInt32 high_perf_lock_acq_duration_sec_histogram = 3;
+
+ // Histogram of LOW_LATENCY lock acquisition duration (seconds)
+ // Note that acquiring the lock does not necessarily mean that device is actively in that mode
+ repeated HistogramBucketInt32 low_latency_lock_acq_duration_sec_histogram = 4;
+
+ // Histogram of HIGH_PERF active session duration (seconds)
+ // This means the lock takes effect and the device takes the actions required for this mode
+ repeated HistogramBucketInt32 high_perf_active_session_duration_sec_histogram = 5;
+
+ // Histogram of LOW_LATENCY active session duration (seconds)
+ // This means the lock takes effect and the device takes the actions required for this mode
+ repeated HistogramBucketInt32 low_latency_active_session_duration_sec_histogram = 6;
+}