Commit cc2246cf authored by davidben@chromium.org's avatar davidben@chromium.org

Update FTP server type histograms in histograms.xml

They were changed in https://chromiumcodereview.appspot.com/11360211, but
histograms.xml reflects the old one.

BUG=none

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278550 0039d316-1c4b-4281-b951-d872f2087c98
parent e265e467
...@@ -13508,10 +13508,19 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -13508,10 +13508,19 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</histogram> </histogram>
<histogram name="Net.FtpServerTypeCount" enum="FtpServerType"> <histogram name="Net.FtpServerTypeCount" enum="FtpServerType">
<obsolete>
Replaced by Net.FtpServerTypeCount2 on 2012-11-03.
</obsolete>
<owner>phajdan.jr@chromium.org</owner>
<summary>
Each bucket is the number of times the FTP server type was encountered.
</summary>
</histogram>
<histogram name="Net.FtpServerTypeCount2" enum="FtpServerType2">
<owner>phajdan.jr@chromium.org</owner> <owner>phajdan.jr@chromium.org</owner>
<summary> <summary>
Each bucket is the number of FTP server types the user has encountered Each bucket is the number of times the FTP server type was encountered.
during the session.
</summary> </summary>
</histogram> </histogram>
...@@ -13572,10 +13581,21 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -13572,10 +13581,21 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</histogram> </histogram>
<histogram name="Net.HadFtpServerType" enum="FtpServerType"> <histogram name="Net.HadFtpServerType" enum="FtpServerType">
<obsolete>
Replaced by Net.HadFtpServerType2 on 2012-11-13.
</obsolete>
<owner>phajdan.jr@chromium.org</owner> <owner>phajdan.jr@chromium.org</owner>
<summary> <summary>
Each bucket is a boolean (0 or 1) indicating whether the user has had a Each bucket is the number of sessions that encountered a given FTP server
connection with an FTP server of that type during the session. type. Each session reports a given server type at most once.
</summary>
</histogram>
<histogram name="Net.HadFtpServerType2" enum="FtpServerType2">
<owner>phajdan.jr@chromium.org</owner>
<summary>
Each bucket is the number of sessions that encountered a given FTP server
type. Each session reports a given server type at most once.
</summary> </summary>
</histogram> </histogram>
...@@ -37821,8 +37841,12 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -37821,8 +37841,12 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</enum> </enum>
<enum name="FtpServerType" type="int"> <enum name="FtpServerType" type="int">
<obsolete>
Deprecated 2012-11-13. No longer generated.
</obsolete>
<summary> <summary>
FTP server type as defined in net/ftp/ftp_server_type_histograms.h Old FTP server type as previously defined in
net/ftp/ftp_server_type_histograms.h
</summary> </summary>
<int value="0" label="Unknown"> <int value="0" label="Unknown">
Unknown (could be a server we don't support, a broken server, or a security Unknown (could be a server we don't support, a broken server, or a security
...@@ -37842,6 +37866,18 @@ Therefore, the affected-histogram name has to have at least one dot in it. ...@@ -37842,6 +37866,18 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</int> </int>
</enum> </enum>
<enum name="FtpServerType2" type="int">
<summary>
FTP server type as defined in net/ftp/ftp_server_type_histograms.h
</summary>
<int value="0" label="Unknown"/>
<int value="1" label="/bin/ls"/>
<int value="2" label="Windows"/>
<int value="3" label="VMS"/>
<int value="4" label="Netware"/>
<int value="5" label="OS/2"/>
</enum>
<enum name="GaiaSessionRestoreOutcome" type="int"> <enum name="GaiaSessionRestoreOutcome" type="int">
<int value="0" label="Undefined"/> <int value="0" label="Undefined"/>
<int value="1" label="Success"/> <int value="1" label="Success"/>
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