tools/metrics/histograms/histograms.xml - Issue 1136523004: [Sessions] Add detailed logging of SessionRestore events.

Unified Diff: tools/metrics/histograms/histograms.xml

Issue 1136523004: [Sessions] Add detailed logging of SessionRestore events. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Sweeping refactor. Created 5 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Download patch

Index: tools/metrics/histograms/histograms.xml

diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml

index abad9a68c327dee0384fa809915ad2d502aae042..a81518ebb1d1f141654211f0b63175548531535f 100644

--- a/tools/metrics/histograms/histograms.xml

+++ b/tools/metrics/histograms/histograms.xml

@@ -605,16 +605,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Ash.AppList.TimeBetweenTaskSwitches" units="seconds">

- <owner>bruthig@chromium.org</owner>

- <owner>tdanderson@chromium.org</owner>

- <summary>

- The amount of time between selecting an item from the Ash app list. Not

- recorded on the first time an item is selected from the app list after

- startup.

- </summary>

-</histogram>

<owner>kuscher@google.com</owner>

<owner>varkha@chromium.org</owner>

@@ -795,16 +785,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>The duration of mostly stationary long-duration touches.</summary>

</histogram>

-<histogram name="Ash.Tab.TimeBetweenSwitchToExistingTabUserActions"

- units="seconds">

- <owner>bruthig@chromium.org</owner>

- <owner>tdanderson@chromium.org</owner>

- <summary>

- The number of seconds between tab switches triggered by a user gesture (e.g.

- Ctrl+T, Ctrl+1, tapping or clicking the tab strip, etc).

- </summary>

-</histogram>

Deprecated 12/2013 in r239809, and replaced by Ash.TouchDuration2.

@@ -936,16 +916,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Ash.WindowCycleController.TimeBetweenTaskSwitches"

- units="seconds">

- <owner>tdanderson@google.com</owner>

- <owner>bruthig@google.com</owner>

- <summary>

- The number of seconds between task switches triggered by the next window and

- previous window accelerator keys (ie Alt+Tab, Alt+Shift+Tab).

- </summary>

-</histogram>

<owner>flackr@chromium.org</owner>

<owner>tdanderson@chromium.org</owner>

@@ -1026,25 +996,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Ash.WindowSelector.TimeBetweenActiveWindowChanges"

- units="seconds">

- <owner>bruthig@chromium.org</owner>

- <owner>tdanderson@chromium.org</owner>

- <summary>

- The amount of time between endings of overview mode sessions which were

- caused by the user selecting a window which was not previously active. Only

- recorded on the second and later times after startup that the user selected

- a window which was not previously active.

- </summary>

-</histogram>

<owner>flackr@chromium.org</owner>

<owner>kuscher@google.com</owner>

- The amount of time between uses of overview mode, recorded when overview

- mode is entered. Only recorded on the second and later times after startup

- that the user entered overview mode.

+ The amount of time between uses of overview mode to switch between windows.

</summary>

</histogram>

@@ -2037,69 +1993,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Autofill.MacAddressBook.AcceptedSuggestionIsFromAddressBook"

- enum="BooleanFromAddressBook">

- <owner>erikchen@chromium.org</owner>

- <summary>

- This metric is emitted each time the user accepts an Autofill suggestion. It

- records whether the result is from the Address Book.

- </summary>

-</histogram>

-<histogram name="Autofill.MacAddressBook.AccessTime" units="ms">

- <owner>erikchen@chromium.org</owner>

- <summary>

- The amount of time spent accessing the OSX Address Book the first time after

- Chrome was launched. If this time is larger than ~100ms, this it is likely

- that the user was shown a blocking, modal dialog.

- </summary>

-</histogram>

-<histogram name="Autofill.MacAddressBook.ContainedMeCard"

- enum="BooleanContainedMeCard">

- <owner>erikchen@chromium.org</owner>

- <summary>

- After a Chrome is given access to the Mac Address Book, whether the Address

- Book contained a Me card.

- </summary>

-</histogram>

-<histogram name="Autofill.MacAddressBook.MeCard.HadAddress"

- enum="BooleanHadAddress">

- <owner>erikchen@chromium.org</owner>

- <summary>

- When Chrome is given access to the Me Card of the Address Book, whether the

- card has an address that contained a street number and either a city or zip

- code.

- </summary>

-</histogram>

-<histogram name="Autofill.MacAddressBook.MeCard.HadEmail"

- enum="BooleanHadEmail">

- <owner>erikchen@chromium.org</owner>

- <summary>

- When Chrome is given access to the Me Card of the Address Book, whether the

- card has an email.

- </summary>

-</histogram>

-<histogram name="Autofill.MacAddressBook.MeCard.HadName" enum="BooleanHadName">

- <owner>erikchen@chromium.org</owner>

- <summary>

- When Chrome is given access to the Me Card of the Address Book, whether the

- card has a name.

- </summary>

-</histogram>

-<histogram name="Autofill.MacAddressBook.MeCard.HadPhoneNumber"

- enum="BooleanHadPhoneNumber">

- <owner>erikchen@chromium.org</owner>

- <summary>

- When Chrome is given access to the Me Card of the Address Book, whether the

- card has a phone number.

- </summary>

-</histogram>

<owner>erikchen@chromium.org</owner>

@@ -3959,22 +3852,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Cookie.Shutdown.NumberOfCookiesDeleted">

- <owner>erikchen@chromium.org</owner>

- <summary>

- The number of session cookies deleted on shutdown. This metric is emitted

- even if no cookies are deleted.

- </summary>

-</histogram>

-<histogram name="Cookie.Shutdown.TimeSpentDeletingCookies" units="ms">

- <owner>erikchen@chromium.org</owner>

- <summary>

- The amount of time required to delete session cookies on shutdown. This

- metric is emitted even if no cookies are deleted.

- </summary>

-</histogram>

<owner>erikchen@chromium.org</owner>

@@ -4221,14 +4098,14 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>dzhioev@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

Records the number of times when first-run dialog was shown.

</summary>

</histogram>

- <owner>dzhioev@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

Index of furthest step that was reached during tutorial. Since order of

steps could change eventially and new steps could apear we use index here

@@ -4237,23 +4114,23 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>dzhioev@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

<summary>The total time that user spent on first-run tutorial.</summary>

</histogram>

- <owner>dzhioev@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

<summary>The time that user spent on some step of tutorial.</summary>

</histogram>

<histogram name="CrosFirstRun.TutorialCompletion"

enum="CrosFirstRunTutorialCompletionType">

- <owner>dzhioev@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

<summary>Tracks the way how user left tutorial.</summary>

</histogram>

- <owner>dzhioev@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

Records the number of times when first-run tutorial has been launched.

</summary>

@@ -4421,41 +4298,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="DataReductionProxy.ConfigFetchLostBytesCL">

- <owner>jeremyim@chromium.org</owner>

- <owner>bengr@chromium.org</owner>

- <summary>

- Size of the response body. This is the actual number of bytes received,

- which usually agrees with but is not necessarily the same as the size

- specified by the Content-Length header. Only recorded if the request is sent

- while a simulated Data Reduction Proxy configuration fetch is taking place.

- </summary>

-</histogram>

-<histogram name="DataReductionProxy.ConfigFetchLostBytesDiff">

- <owner>jeremyim@chromium.org</owner>

- <owner>bengr@chromium.org</owner>

- <summary>

- The difference between the size specified in the X-Original-Content-Length

- header and the size of the response body. Only recorded if the request is

- sent while a simulated Data Reduction Proxy configuration fetch is taking

- place. Only positive values are logged, so if X-Original-Content-Length is

- not specified or if it equals or exceeds the content length, it is not

- logged.

- </summary>

-</histogram>

-<histogram name="DataReductionProxy.ConfigFetchLostBytesOCL">

- <owner>jeremyim@chromium.org</owner>

- <owner>bengr@chromium.org</owner>

- <summary>

- Size specified in the X-Original-Content-Length header. If this header is

- not present in the response, the size of the response body is used. Only

- recorded if the request is sent while a simulated Data Reduction Proxy

- configuration fetch is taking place.

- </summary>

-</histogram>

<histogram

name="DataReductionProxy.ConfigService.FetchFailedAttemptsBeforeSuccess">

<owner>jeremyim@chromium.org</owner>

@@ -12149,15 +11991,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="GPU.ANGLE.D3D11CreateDeviceError" units="D3DHresult">

- <owner>jmadill@chromium.org</owner>

- <summary>

- An extended Windows error code returned from D3D11CreateDevice on error. Can

- be almost any valid HRESULT or DXGI error code, which are listed at

- https://msdn.microsoft.com/en-us/library/windows/desktop/bb509553.aspx.

- </summary>

-</histogram>

<owner>jmadill@chromium.org</owner>

@@ -12167,16 +12000,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="GPU.ANGLE.D3D11FeatureLevel" units="D3DFeatureLevel">

- <owner>jmadill@chromium.org</owner>

- <summary>

- The maxmium supported (or currently requested) Direct3D feature level in

- D3D11 ANGLE. We support as low as 9.3, and as high as 11.1, though Chrome

- should only use 10.0+ for D3D11. Gives an indication of how new a user's

- video card is, what features it supports, and it's general speed tier.

- </summary>

-</histogram>

<owner>jmadill@chromium.org</owner>

@@ -12193,15 +12016,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="GPU.ANGLE.SupportsDXGI1_2" units="BooleanSupported">

- <owner>jmadill@chromium.org</owner>

- <summary>

- Windows computers running Windows 8+, or running Windows 7 with a platform

- update, support the newer version of DXGI. This update also indicates the

- computer is capable of running Direct3D 11.1 if the hardware supports it.

- </summary>

-</histogram>

<owner>vangelis@chromium.org</owner>

@@ -12678,7 +12492,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="HistoryPage.OtherDevicesMenu" enum="OtherSessionsActions">

+<histogram name="HistoryPage.OtherDevicesMenu" enum="NtpOtherSessionsType">

<owner>mad@chromium.org</owner>

<owner>rpop@google.com</owner>

@@ -13824,10 +13638,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<owner>felt@chromium.org</owner>

- <summary>

- User decision when presented with a security interstitial. As of M44,

- subresource interstitials were split into their own entries.

- </summary>

+ <summary>User decision when presented with a security interstitial.</summary>

</histogram>

<histogram name="interstitial.decision.repeat_visit"

@@ -13835,18 +13646,14 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<owner>felt@chromium.org</owner>

User decision when presented with a security interstitial, on a site that

- the user had previously visited. As of M44, subresource interstitials were

- split into their own entries.

+ the user had previously visited.

</summary>

</histogram>

<histogram name="interstitial.interaction"

enum="SecurityInterstitialInteraction">

<owner>felt@chromium.org</owner>

- <summary>

- User interactions with a security interstitial. As of M44, subresource

- interstitials were split into their own entries.

- </summary>

+ <summary>User interactions with a security interstitial.</summary>

</histogram>

@@ -14555,20 +14362,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Login.NewUserPriorityPrefsSyncResult"

- enum="NewUserPriorityPrefsSyncResult">

- <owner>dzhioev@chromeos.org</owner>

- <summary>Records whether a new user's priority prefs sync timed out.</summary>

-</histogram>

-<histogram name="Login.NewUserPriorityPrefsSyncTime" units="milliseconds">

- <owner>dzhioev@chromeos.org</owner>

- <summary>

- Time spent waiting for priority preferences to sync after new user sign in.

- The operation will time out after 10s.

- </summary>

-</histogram>

<owner>cmasone@chromium.org</owner>

<summary>The state of Chrome OS owner key and device policy files.</summary>

@@ -16553,9 +16346,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated and removed from code as of 05/2015.

- </obsolete>

<owner>anthonyvd@chromium.org</owner>

Represents the difference in bytes deemed modified by the two

@@ -19605,17 +19395,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Net.GoogleConnectionInappropriateFallback"

- enum="BooleanInappropriateFallback">

- <owner>davidben@chromium.org</owner>

- <summary>

- Records a sample for each HTTPS request to a Google server that either

- succeeded or received an inappropriate_fallback alert. This is used to

- estimate how frequently the fallback is used to recover from a spurious

- network failure.

- </summary>

-</histogram>

<histogram name="Net.GoogleConnectionUsedSSLVersionFallback"

enum="FallbackSSLVersion">

@@ -19636,8 +19415,8 @@ Therefore, the affected-histogram name has to have at least one dot in it.

For each successful HTTPS request to a Google server, whether it used the

SSL version fallback. The value indicates the SSL version the request fell

- back on. Since Google servers support TLS 1.2 and FALLBACK_SCSV, any

- fallback is an indication of a broken local SSL MITM proxy.

+ back on. Since Google servers support TLS 1.2, any fallback is an indication

+ of network middleware problems.

</summary>

</histogram>

@@ -20427,14 +20206,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Net.PrefProxyConfig.GooglezipProxyRemovalCount">

- <owner>sclittle@chromium.org</owner>

- <summary>

- Records how many *.googlezip.net Data Reduction Proxies were removed from

- the effective proxy configuration when a proxy reconfiguration occurs.

- </summary>

-</histogram>

Replaced by Net.Priority_High_Latency_b.

@@ -22349,22 +22120,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Time to complete a certificate verification (error case).</summary>

</histogram>

-<histogram name="Net.SSLFallbackErrorCode" enum="NetErrorCodes">

- <owner>davidben@chromium.org</owner>

- <summary>

- For each successful HTTPS request which used the TLS version fallback, the

- error code of the last failed attempt.

- </summary>

-</histogram>

-<histogram name="Net.SSLFallbackFailureState" enum="SSLFailureState">

- <owner>davidben@chromium.org</owner>

- <summary>

- For each successful HTTPS request which used the TLS version fallback, the

- type of handshake failure of the last failed attempt.

- </summary>

-</histogram>

<owner>Please list the metric's owners. Add more owner tags as needed.</owner>

<summary>Time to complete a DNS lookup for a DNS CAA record.</summary>

@@ -25278,11 +25033,8 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="NewTabPage.OtherSessionsMenu" enum="OtherSessionsActions">

+<histogram name="NewTabPage.OtherSessionsMenu" enum="NtpOtherSessionsType">

<owner>Please list the metric's owners. Add more owner tags as needed.</owner>

- <obsolete>

- Deprecated 05/2015. Feature was removed.

- </obsolete>

Histogram for usage of the menu on the NTP that allows the user to access

tabs from other devices.

@@ -25824,7 +25576,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<owner>mpearson@chromium.org</owner>

- The number of terms in the text the user entered in the omnibox when they

+ The number of terms in the text the user entered in the omnibox when he/she

used the omnibox to go somewhere. Terms are defined by splitting on

whitespace. All values larger than 6 are recorded in bucket 6.

</summary>

@@ -26977,14 +26729,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Platform.BatteryAbsent" enum="BooleanAbsent">

- <owner>cernekee@chromium.org</owner>

- <summary>

- Indicates whether the kernel's ACPI Smart Battery System driver logged an

- error trying to find the battery on boot.

- </summary>

-</histogram>

<owner>sonnyrao@chromium.org</owner>

@@ -29592,7 +29336,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Collects Flash usage data.</summary>

</histogram>

-<histogram name="Plugin.NpapiRemovalInfobar.Removed.PluginGroup"

+<histogram name="Plugin.NPAPIRemovalInfobar.Removed.PluginGroup"

enum="PluginGroup">

<owner>wfh@chromium.org</owner>

@@ -29602,7 +29346,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Plugin.NpapiRemovalInfobar.RemovedSoon.PluginGroup"

+<histogram name="Plugin.NPAPIRemovalInfobar.RemovedSoon.PluginGroup"

enum="PluginGroup">

<owner>wfh@chromium.org</owner>

@@ -36374,14 +36118,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="ServiceWorker.UnhandledEventRatio" units="percent">

- <owner>kinuko@chromium.org</owner>

- <summary>

- Records the ratio of unhandled events to all events that are dispatched to

- each ServiceWorker. Recorded when each ServiceWorkerVersion is destructed.

- </summary>

-</histogram>

<owner>dmurph@chromium.org</owner>

@@ -36428,6 +36164,15 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>How did the user interact with the SessionCrashed Bubble?</summary>

</histogram>

+<histogram name="SessionRestore.Actions" enum="SessionRestoreActions">

+ <owner>chrisha@chromium.org</owner>

+ <summary>

+ The actions that have occurred in a session restore timeline. These are to

+ be interpreted as raw event counts. Tabs are almost certainly deferred due

+ to the existence memory pressure, but this may not always be the case.

+ </summary>

+</histogram>

<owner>jeremy@chromium.org</owner>

<owner>sky@chromium.org</owner>

@@ -36446,7 +36191,8 @@ Therefore, the affected-histogram name has to have at least one dot in it.

- Deprecated 2014-10 in favor of SessionRestore.ForegroundTabFirstPaint.

+ Deprecated 2014-10 in favor of SessionRestore.ForegroundTabFirstPaint and

+ ultimately SessionRestore.ForegroundTabFirstPaint3.

</obsolete>

<owner>jeremy@chromium.org</owner>

<owner>sky@chromium.org</owner>

@@ -36465,11 +36211,25 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<owner>jeremy@chromium.org</owner>

<owner>sky@chromium.org</owner>

- Deprecated 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2.

+ Deprecated 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2

+ and ultimately SessionRestore.ForegroundTabFirstPaint3.

</summary>

</histogram>

+ <obsolete>

+ Deprecated 2015-05 in favor of SessionRestore.ForegroundTabFirstPaint3.

+ </obsolete>

+ <owner>jeremy@chromium.org</owner>

+ <owner>sky@chromium.org</owner>

+ <summary>

+ The time from SessionRestore start until a visible tab's first paint. This

+ metric only records paints that have occurred after a tab has loaded.

+ </summary>

+</histogram>

+<histogram name="SessionRestore.ForegroundTabFirstPaint3" units="milliseconds">

+ <owner>chrisha@chromium.org</owner>

<owner>jeremy@chromium.org</owner>

<owner>sky@chromium.org</owner>

@@ -36558,6 +36318,14 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</details>

</histogram>

+<histogram name="SessionRestore.TabActions" enum="SessionRestoreTabActions">

+ <owner>chrisha@chromium.org</owner>

+ <summary>

+ A breakdown of exactly how different tabs were treated during session

+ restore events.

+ </summary>

+</histogram>

<owner>jeremy@chromium.org</owner>

<owner>sky@chromium.org</owner>

@@ -36575,6 +36343,13 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

+<histogram name="SessionRestore.TabCount" units="tabs">

+ <owner>chrisha@chromium.org</owner>

+ <summary>

+ The number of tabs involved in a single session restore event.

+ </summary>

+</histogram>

<owner>michaeln@chromium.org</owner>

@@ -37204,49 +36979,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Track how a profile gets signed out.</summary>

</histogram>

-<histogram name="Signin.XDevicePromo.BrowsingSessionDuration" units="minutes">

- <owner>anthonyvd@chromium.org</owner>

- <owner>mlerman@chromium.org</owner>

- <summary>

- How long a browsing session was measured to be. Logged when a Browser window

- becomes active if the previous activation was longer than the minimum

- configured in the "CrossDevicePromo" experiment. Desktop only.

- </summary>

-</histogram>

-<histogram name="Signin.XDevicePromo.BrowsingSessionDurationComputed"

- units="minutes">

- <owner>anthonyvd@chromium.org</owner>

- <owner>mlerman@chromium.org</owner>

- <summary>

- How often browsers are considered activated, which in turn triggers the

- CrossDevicePromo. Logged every time a Browser window becomes active. We need

- this to estimate QPS for RPC calls. Desktop only.

- </summary>

-</histogram>

-<histogram name="Signin.XDevicePromo.Eligibility"

- enum="SigninXDevicePromoEligibility">

- <owner>anthonyvd@chromium.org</owner>

- <owner>mlerman@chromium.org</owner>

- <summary>

- The reasons for which a profile is or is not eligible for the Desktop Cross

- Device Sign In Promo. Logged every time a new Browsing session is detected

- as part of a Browser window becoming active. Desktop only.

- </summary>

-</histogram>

-<histogram name="Signin.XDevicePromo.Initialized"

- enum="SigninXDevicePromoInitialized">

- <owner>anthonyvd@chromium.org</owner>

- <owner>mlerman@chromium.org</owner>

- <summary>

- Tracks if profiles initialized the XDevicePromo, and if not, why. Logged at

- Profile startup and (if not initialized then) when a new browsing session is

- detected during Browser window activation. Desktop only.

- </summary>

-</histogram>

<owner>gavinp@chromium.org</owner>

@@ -41995,36 +41727,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Sync.MemoryPressureWarningBeforeCleanShutdown" units="count">

- <owner>gangwu@chromium.org</owner>

- <summary>

- Counts the number of times a user's sync service received a

- MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down

- cleanly. The sync service emits this number the next time the user's sync

- service is started, which will likely happen the next time the user's

- profile is opened after a Chrome restart. This count is emitted once per

- user/profile. Things like browser crashes that implicitly bring down all

- users' sync services will cause unclean shutdown tags to appear on all open

- profiles, meaning that there will be multiple emissions to this histogram as

- those profiles are re-opened.

- </summary>

-</histogram>

-<histogram name="Sync.MemoryPressureWarningBeforeUncleanShutdown" units="count">

- <owner>gangwu@chromium.org</owner>

- <summary>

- Counts the number of times a user's sync service received a

- MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down

- uncleanly. The sync service emits this number the next time the user's sync

- service is started, which will likely happen the next time the user's

- profile is opened after a Chrome restart. This count is emitted once per

- user/profile. Things like browser crashes that implicitly bring down all

- users' sync services will cause unclean shutdown tags to appear on all open

- profiles, meaning that there will be multiple emissions to this histogram as

- those profiles are re-opened.

- </summary>

-</histogram>

<owner>zea@chromium.org</owner>

<summary>Breakdown of sync's nigori node keystore migration state.</summary>

@@ -42641,15 +42343,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="SyncPromo.NTPPromo" enum="SyncPromoAction">

- <owner>dbeam@chromium.org</owner>

- <summary>

- Shows actions taken on the "Not signed in? You're misssing out"

- link on the top right of chrome://apps. Logged once per visit of

- chrome://apps as well as on each click of the sync promo.

- </summary>

-</histogram>

<owner>lliabraa@chromium.org</owner>

@@ -48357,11 +48050,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="BooleanAbsent" type="int">

- <int value="0" label="Not Absent"/>

- <int value="1" label="Absent"/>

-</enum>

@@ -48397,11 +48085,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="BooleanContainedMeCard" type="int">

- <int value="0" label="Did not contain me card."/>

- <int value="1" label="Contained me card."/>

-</enum>

@@ -48477,41 +48160,16 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="BooleanFromAddressBook" type="int">

- <int value="0" label="Not From Address Book"/>

- <int value="1" label="From Address Book"/>

-</enum>

</enum>

-<enum name="BooleanHadAddress" type="int">

- <int value="0" label="Did not have address."/>

- <int value="1" label="Had address."/>

-</enum>

</enum>

-<enum name="BooleanHadEmail" type="int">

- <int value="0" label="Did not have email."/>

- <int value="1" label="Had email."/>

-</enum>

-<enum name="BooleanHadName" type="int">

- <int value="0" label="Did not have name."/>

- <int value="1" label="Had name."/>

-</enum>

-<enum name="BooleanHadPhoneNumber" type="int">

- <int value="0" label="Did not have phone number."/>

- <int value="1" label="Had phone number."/>

-</enum>

@@ -48552,11 +48210,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="BooleanInappropriateFallback" type="int">

- <int value="0" label="Handshake successful"/>

- <int value="1" label="inappropriate_fallback alert"/>

-</enum>

@@ -48667,11 +48320,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="BooleanSupported" type="int">

- <int value="0" label="Not Supported"/>

- <int value="1" label="Supported"/>

-</enum>

@@ -49778,51 +49426,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="D3DFeatureLevel" type="int">

- <int value="0" label="D3D_FEATURE_LEVEL_INVALID"/>

- <int value="1" label="D3D_FEATURE_LEVEL_9_3"/>

- <int value="2" label="D3D_FEATURE_LEVEL_10_0"/>

- <int value="3" label="D3D_FEATURE_LEVEL_10_1"/>

- <int value="4" label="D3D_FEATURE_LEVEL_11_0"/>

- <int value="5" label="D3D_FEATURE_LEVEL_11_1"/>

-</enum>

-<enum name="D3DHresult" type="int">

- <int value="-2147467263" label="E_NOTIMPL"/>

- <int value="-2147467262" label="E_NOINTERFACE"/>

- <int value="-2147467261" label="E_POINTER"/>

- <int value="-2147467260" label="E_ABORT"/>

- <int value="-2147467259" label="E_FAIL"/>

- <int value="-2147418113" label="E_UNEXPECTED"/>

- <int value="-2147024891" label="E_ACCESSDENIED"/>

- <int value="-2147024890" label="E_HANDLE"/>

- <int value="-2147024882" label="E_OUTOFMEMORY"/>

- <int value="-2147024809" label="E_INVALIDARG"/>

- <int value="-2005270527" label="DXGI_ERROR_INVALID_CALL"/>

- <int value="-2005270526" label="DXGI_ERROR_NOT_FOUND"/>

- <int value="-2005270525" label="DXGI_ERROR_MORE_DATA"/>

- <int value="-2005270524" label="DXGI_ERROR_UNSUPPORTED"/>

- <int value="-2005270523" label="DXGI_ERROR_DEVICE_REMOVED"/>

- <int value="-2005270522" label="DXGI_ERROR_DEVICE_HUNG"/>

- <int value="-2005270521" label="DXGI_ERROR_DEVICE_RESET"/>

- <int value="-2005270518" label="DXGI_ERROR_WAS_STILL_DRAWING"/>

- <int value="-2005270517" label="DXGI_ERROR_FRAME_STATISTICS_DISJOINT"/>

- <int value="-2005270516" label="DXGI_ERROR_GRAPHICS_VIDPN_SOURCE_IN_USE"/>

- <int value="-2005270496" label="DXGI_ERROR_DRIVER_INTERNAL_ERROR"/>

- <int value="-2005270495" label="DXGI_ERROR_NONEXCLUSIVE"/>

- <int value="-2005270494" label="DXGI_ERROR_NOT_CURRENTLY_AVAILABLE"/>

- <int value="-2005270493" label="DXGI_ERROR_REMOTE_CLIENT_DISCONNECTED"/>

- <int value="-2005270492" label="DXGI_ERROR_REMOTE_OUTOFMEMORY"/>

- <int value="-2005270490" label="DXGI_ERROR_ACCESS_LOST"/>

- <int value="-2005270489" label="DXGI_ERROR_WAIT_TIMEOUT"/>

- <int value="-2005270488" label="DXGI_ERROR_SESSION_DISCONNECTED"/>

- <int value="-2005270487" label="DXGI_ERROR_RESTRICT_TO_OUTPUT_STALE"/>

- <int value="-2005270486" label="DXGI_ERROR_CANNOT_PROTECT_CONTENT"/>

- <int value="-2005270485" label="DXGI_ERROR_ACCESS_DENIED"/>

- <int value="-2005270484" label="DXGI_ERROR_NAME_ALREADY_EXISTS"/>

- <int value="-2005270483" label="DXGI_ERROR_SDK_COMPONENT_MISSING"/>

-</enum>

@@ -52761,7 +52364,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

- <int value="1010" label="FILEMANAGERPRIVATE_CONFIGUREVOLUME"/>

+ <int value="1010" label="FILEMANAGERPRIVATE_CONFIGUREPROVIDEDFILESYSTEM"/>

@@ -56622,11 +56225,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.

- <int value="1" label="Not supported">obsolete</int>

- <int value="2" label="Supported">obsolete</int>

+ <int value="1" label="Not supported"/>

+ <int value="2" label="Supported"/>

- <int value="5" label="Used no map executable support fallback">obsolete</int>

+ <int value="5" label="Used no map executable support fallback"/>

</enum>

@@ -56932,7 +56535,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-1832221649" label="disable-out-of-process-pac"/>

@@ -57008,7 +56610,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-1062119671" label="enable-password-force-saving"/>

@@ -57050,7 +56651,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-610411643" label="enable-printer-app-search"/>

@@ -57239,7 +56839,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1272699563" label="enable-hosted-mode"/>

@@ -59278,11 +58877,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="NewUserPriorityPrefsSyncResult" type="int">

- <int value="0" label="Succeeded"/>

- <int value="1" label="Timed out"/>

-</enum>

@@ -59337,6 +58931,18 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

+<enum name="NtpOtherSessionsType" type="int">

+ <int value="0" label="Menu initialized"/>

+ <int value="1" label="Menu shown"/>

+ <int value="2" label="Link clicked"/>

+ <int value="3" label="Link context menu shown"/>

+ <int value="4" label="Device context menu shown"/>

+ <int value="5" label="Unused/previous device context menu shown"/>

+ <int value="6" label="Collapse Session"/>

+ <int value="7" label="Expand Session"/>

+ <int value="8" label="Open All"/>

+</enum>

@@ -59791,18 +59397,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="OtherSessionsActions" type="int">

- <int value="0" label="Menu initialized"/>

- <int value="1" label="Menu shown"/>

- <int value="2" label="Link clicked"/>

- <int value="3" label="Link context menu shown"/>

- <int value="4" label="Device context menu shown"/>

- <int value="5" label="Unused/previous device context menu shown"/>

- <int value="6" label="Collapse Session"/>

- <int value="7" label="Expand Session"/>

- <int value="8" label="Open All"/>

-</enum>

<summary>Direction of the overscroll gesture.</summary>

<int value="1" label="North">Scrolled from bottom towards top</int>

@@ -61326,10 +60920,7 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1" label="Page displayed (Deprecated)"/>

- <int value="2" label="Printer supported notification shown"/>

- <int value="3" label="Printer not supported notification shown"/>

- <int value="4" label="Printer provider Web Store app launched"/>

+ <int value="1" label="Page displayed"/>

</enum>

@@ -62494,7 +62085,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="66" label="IDC_CONTENT_CONTEXT_SHOW_ORIGINAL_IMAGE"/>

</enum>

@@ -63301,6 +62891,18 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

+<enum name="SessionRestoreActions" type="int">

+ <int value="0" label="A session restore was started"/>

+ <int value="1" label="A session restore deferred one or more tabs"/>

+</enum>

+<enum name="SessionRestoreTabActions" type="int">

+ <int value="0" label="A tab was created"/>

+ <int value="1" label="A tab's content was automatically loaded"/>

+ <int value="2" label="The loading of a tab's content was deferred"/>

+ <int value="3" label="A deferred tab's content was loaded via user action"/>

+</enum>

@@ -63493,42 +63095,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="SigninXDevicePromoEligibility" type="int">

- <int value="0" label="Eligible">The user is eligible for the promo.</int>

- <int value="1" label="Opted Out">

- The profile has previously opted out of the promo.

- </int>

- <int value="2" label="Signed In">The profile is already signed in.</int>

- <int value="3" label="Not Single GAIA Account">

- The profile does not have a single, peristent GAIA cookie.

- </int>

- <int value="4" label="Unknown count of devices">

- Yet to determine how many devices the user has.

- </int>

- <int value="5" label="Error fetching device activity">

- An error was returned trying to determine the account's devices.

- </int>

- <int value="6" label="Throttled fetching device activity">

- The call to get device activity was throttled, and never executed.

- </int>

- <int value="7" label="Zero devices found">The user has no devices.</int>

- <int value="8" label="No devices active">

- The user has no device that was recently active.

- </int>

-</enum>

-<enum name="SigninXDevicePromoInitialized" type="int">

- <int value="0" label="Initialized">

- The promo was initialized successfully.

- </int>

- <int value="1" label="Opted Out">

- The profile is opted out, so the promo didn't initialize.

- </int>

- <int value="2" label="No variations config">

- Unable to read the variations configuration.

- </int>

-</enum>

@@ -64581,16 +64147,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="SSLFailureState" type="int">

- <int value="0" label="No failure"/>

- <int value="1" label="Unknown failure"/>

- <int value="2" label="Failed to process ClientHello"/>

- <int value="3" label="Buggy AES-GCM"/>

- <int value="4" label="Failed with client authentication"/>

- <int value="5" label="Session version mismatch"/>

- <int value="6" label="Failed with Next Proto Negotiation"/>

-</enum>

@@ -65156,11 +64712,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="SyncPromoAction" type="int">

- <int value="0" label="The promo was shown to the user"/>

- <int value="1" label="The user clicked the promo to sign in"/>

-</enum>

Sync simple conflict resolutions. The codes are listed in

@@ -67156,22 +66707,6 @@ To add a new entry, add it with any value and run test to compute valid value.

<affected-histogram name="DataReductionProxy.BypassedBytes"/>

</histogram_suffixes>

-<histogram_suffixes name="DataReductionProxyConfigFetchLostBytes" separator="_">

- <suffix name="0" label="Bucket 0 for gathering multiple data points."/>

- <suffix name="1" label="Bucket 1 for gathering multiple data points."/>

- <suffix name="2" label="Bucket 2 for gathering multiple data points."/>

- <suffix name="3" label="Bucket 3 for gathering multiple data points."/>

- <suffix name="4" label="Bucket 4 for gathering multiple data points."/>

- <suffix name="5" label="Bucket 5 for gathering multiple data points."/>

- <suffix name="6" label="Bucket 6 for gathering multiple data points."/>

- <suffix name="7" label="Bucket 7 for gathering multiple data points."/>

- <suffix name="8" label="Bucket 8 for gathering multiple data points."/>

- <suffix name="9" label="Bucket 9 for gathering multiple data points."/>

- <affected-histogram name="DataReductionProxy.ConfigFetchLostBytesCL"/>

- <affected-histogram name="DataReductionProxy.ConfigFetchLostBytesDiff"/>

- <affected-histogram name="DataReductionProxy.ConfigFetchLostBytesOCL"/>

-</histogram_suffixes>

<histogram_suffixes name="DataReductionProxyMissingViaHeaderBytes"

separator=".">

@@ -68080,12 +67615,8 @@ To add a new entry, add it with any value and run test to compute valid value.

label="The version of the Module Integrity Verifier that doesn't use a

hash set to track relocations."/>

<suffix name="WithByteSet"

- label="The version of the Module Integrity Verifier that uses a hash set

- to track relocations.">

- <obsolete>

- Deprecated and removed from code as of 05/2015.

- </obsolete>

- </suffix>

+ label="The version of the Module Integrity Verifier that uses a hash

+ set to track relocations."/>

<affected-histogram name="ModuleIntegrityVerification.BytesModified"/>

<affected-histogram name="ModuleIntegrityVerification.Difference"/>

</histogram_suffixes>

@@ -70477,11 +70008,8 @@ To add a new entry, add it with any value and run test to compute valid value.

ordering="prefix">

- <suffix name="harmful_subresource"/>

- <suffix name="malware_subresource"/>

- <suffix name="phishing_subresource"/>

<affected-histogram name="interstitial.decision"/>

@@ -70550,6 +70078,7 @@ To add a new entry, add it with any value and run test to compute valid value.

<affected-histogram name="SessionRestore.ForegroundTabFirstLoaded"/>

<affected-histogram name="SessionRestore.ForegroundTabFirstPaint"/>

<affected-histogram name="SessionRestore.ForegroundTabFirstPaint2"/>

+ <affected-histogram name="SessionRestore.ForegroundTabFirstPaint3"/>

</histogram_suffixes>

<histogram_suffixes name="ShillWiFiRememberedNetworkSecurityMode" separator=".">

« chrome/browser/sessions/session_restore_stats_collector.cc ('K') | « chrome/browser/sessions/tab_loader.cc ('k') | no next file » | no next file with comments »