Commit af6ef5f4 authored by zqiu@chromium.org's avatar zqiu@chromium.org

Network performance related histograms.

Added a histogram "Network.Shill.DeviceConnectionStatus" for tracking the
connection status of the device. A sample is emitted once every 3
minutes.

Added a histogram "Network.Shill.Wifi.NetworkProblemDetected" for tracking
the connection problem encountered by TrafficMonitor after the wifi
connection is established. This event is reported whenever a network
problem is encountered while connected to a  wifi network.

Added a histogram "NetworkShill.WiFi.UserInitiatedConnectionFailureReason"
for tracking the reasons for failed wifi connection attempts that are
manually initiated by the user. This event is reported everytime
user-initiated wifi connection attempts failed.

BUG=chromium:374274, chromium:392965, chromium:392990
TEST=Start chrome, and browse to chrome://histograms to verify the
histograms mentioned above exist.
NOTRY=true

Review URL: https://codereview.chromium.org/429353002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287826 0039d316-1c4b-4281-b951-d872f2087c98
parent 5b24aa9d
...@@ -17653,6 +17653,14 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -17653,6 +17653,14 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</summary> </summary>
</histogram> </histogram>
<histogram name="Network.Shill.DeviceConnectionStatus" enum="ConnectionStatus">
<owner>zqiu@chromium.org</owner>
<summary>
Chrome OS network performance metric that tracks the connection status of
the device. A sample is emitted once every 3 minutes.
</summary>
</histogram>
<histogram name="Network.Shill.DHCPClientStatus" enum="NetworkDhcpClientStatus"> <histogram name="Network.Shill.DHCPClientStatus" enum="NetworkDhcpClientStatus">
<owner>pstew@chromium.org</owner> <owner>pstew@chromium.org</owner>
<summary> <summary>
...@@ -18131,6 +18139,15 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -18131,6 +18139,15 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</summary> </summary>
</histogram> </histogram>
<histogram name="Network.Shill.Wifi.NetworkProblemDetected"
enum="NetworkProblemType">
<owner>zqiu@chromium.org</owner>
<summary>
Chrome OS network performance metric that tracks the network problems
encountered by TrafficMonitor after WiFi connection is established.
</summary>
</histogram>
<histogram name="Network.Shill.Wifi.PhyMode" enum="NetworkPhyModeType"> <histogram name="Network.Shill.Wifi.PhyMode" enum="NetworkPhyModeType">
<owner>quiche@chromium.org</owner> <owner>quiche@chromium.org</owner>
<summary> <summary>
...@@ -18303,12 +18320,23 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -18303,12 +18320,23 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</summary> </summary>
</histogram> </histogram>
<histogram name="Network.Shill.WiFi.UserInitiatedConnectionFailureReason"
enum="ConnectionFailureReason">
<owner>zqiu@chromium.org</owner>
<summary>
Chrome OS network performance metric that tracks the reasons of failed
user-initiated WiFi connection attempts. The result of the user-initiated
WiFi connection attempts are being tracked by
Network.Shill.WiFi.UserInitiatedConnectionResult.
</summary>
</histogram>
<histogram name="Network.Shill.WiFi.UserInitiatedConnectionResult" <histogram name="Network.Shill.WiFi.UserInitiatedConnectionResult"
enum="ConnectionResult"> enum="ConnectionResult">
<owner>zqiu@chromium.org</owner> <owner>zqiu@chromium.org</owner>
<summary> <summary>
Chrome OS network performance metric that tracks the result of Chrome OS network performance metric that tracks the result of
user-initiated wifi connection attempts. user-initiated WiFi connection attempts.
</summary> </summary>
</histogram> </histogram>
...@@ -37069,12 +37097,32 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -37069,12 +37097,32 @@ Therefore, the affected-histogram name has to have at least one dot in it.
<int value="1" label="GPU compositor"/> <int value="1" label="GPU compositor"/>
</enum> </enum>
<enum name="ConnectionFailureReason" type="int">
<int value="0" label="Unknown"/>
<int value="1" label="Bad Passphrase"/>
<int value="2" label="Bad WEP Key"/>
<int value="3" label="Failed to Connect"/>
<int value="4" label="DHCP Failure"/>
<int value="5" label="DNS Lookup Failure"/>
<int value="6" label="EAP Authentication"/>
<int value="7" label="EAP Local TLS"/>
<int value="8" label="EAP Remote TLS"/>
<int value="9" label="Out-of-range"/>
<int value="10" label="Pin Missing"/>
</enum>
<enum name="ConnectionResult" type="int"> <enum name="ConnectionResult" type="int">
<int value="0" label="Success"/> <int value="0" label="Success"/>
<int value="1" label="Failure"/> <int value="1" label="Failure"/>
<int value="2" label="Aborted"/> <int value="2" label="Aborted"/>
</enum> </enum>
<enum name="ConnectionStatus" type="int">
<int value="0" label="Offline"/>
<int value="1" label="Connected"/>
<int value="2" label="Online"/>
</enum>
<enum name="ConnectionType" type="int"> <enum name="ConnectionType" type="int">
<summary> <summary>
Connection type as defined in net/base/connection_type_histograms.h Connection type as defined in net/base/connection_type_histograms.h
...@@ -44098,6 +44146,11 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -44098,6 +44146,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.
<int value="9" label="Unknown"/> <int value="9" label="Unknown"/>
</enum> </enum>
<enum name="NetworkProblemType" type="int">
<int value="0" label="Congested TCP Queue"/>
<int value="1" label="DNS Failure"/>
</enum>
<enum name="NetworkSecurityType" type="int"> <enum name="NetworkSecurityType" type="int">
<summary> <summary>
The security types come from the connman_service_security enum in The security types come from the connman_service_security enum in
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment