victorvianna@google.com src/components/sync/OWNERS Services>Sync Logged when a data type is backed off. This histogram can help explain changes in Sync.PostedClientToServerMessageError2::PARTIAL_FAILURE. ankushkush@google.com src/components/sync/OWNERS Services>Sync Logged when batch upload of local data for a data type is requested. Note that at the time of writing, this metric only supports PASSWORDS, BOOKMARKS and READING_LIST. rushans@google.com mastiz@chromium.org Services>Sync Records if the entity is marked to be reuploaded. It is recorded on each incoming bookmark update from the server during {UpdateType}. rushans@google.com mastiz@chromium.org Services>Sync Records whether a GUID was found within BookmarkSpecifics, if an originator_client_item_id of valid GUID format was used to replace it, or if the field was left empty. Recorded when processing a remote bookmark update, except for permanent nodes, which are created server-side and don't have an originator client item ID. rushans@google.com mastiz@chromium.org Services>Sync Records the number of valid and non-duplicate updates processed during initial merge for bookmarks that are reachable when traversing the bookmark tree, including permanent folders. Recorded during the initial merge procedure after deduplication. rushans@google.com mastiz@chromium.org Services>Sync Records the number of unsynced entities (bookmarks or folders) as a result of the initial merge for bookmarks. This includes local creations (i.e. did not match any entity in the server) as well as local modifications (e.g. pending reupload). Recorded upon completion of the initial merge procedure. rushans@google.com mastiz@chromium.org Services>Sync Records the number of received input updates considered valid during initial merge for bookmarks, prior to deduplication, including permanent folders and unreachable nodes (see Sync.BookmarkModelMerger.ReachableInputUpdates for a more strict variant). Invalid updates contribute to metric Sync.ProblematicServerSideBookmarksDuringMerge. Recorded during the initial merge procedure. rushans@google.com mastiz@chromium.org Services>Sync Measures the initial bookmark merge time broken down by different stages. Recorded after every initial merge procedure {UpdatesCount}. mastiz@chromium.org rushans@google.com Services>Sync Records different types of bookmark entities having the same GUIDs. It's recorded on each found duplicate when processing remote bookmarks from the sync server during the initial merge. rushans@google.com mastiz@chromium.org Services>Sync The reason why the persisted metadata for a bookmark model is considered corrupted. It either has corrupted data or doesn't match the bookmark model. It's recorded at start up only if the initial sync has been performed already. It's recorded after loading the metadata. rushans@google.com mastiz@chromium.org Services>Sync Records if a remote sync update for a bookmark, excluding folders, contains a favicon. It is recorded upon initial and incremental updates, when the local state is about to be modified. ankushkush@google.com treib@chromium.org Services>Sync Recorded when metadata is cleared upon ModelReadyToSync() in the case where clearing of metadata was requested before ModelReadyToSync() while the data type was not running. ankushkush@google.com treib@chromium.org Services>Sync Recorded whenever clearing of metadata is requested while the data type is not running and the metadata is cleared immediately. treib@chromium.org mastiz@chromium.org Services>Sync Emitted when a Commit entity response is received for an unknown entity (i.e. for a client tag hash that doesn't correspond to a tracked entity). rushans@google.com treib@chromium.org Services>Sync Emitted per network Commit() request to the sync server and datatype. Records the outcome of each commit attempt per data type (success or one of various error codes). mastiz@chromium.org treib@chromium.org Services>Sync Whether the full Sync feature or only the Sync transport layer is being configured. Recorded when configuring the data types for any reason: Most commonly during browser startup, but also after initial setup, after a reconfiguration by the user, or when switching between full feature mode and transport mode. mastiz@chromium.org treib@chromium.org Services>Sync Breakdown of sync data types being configured at first time signin, restart, or user-initiated reconfiguration. This is different from Sync.CustomTypes in that this captures all active devices, not just those that are choosing a custom sync configuration. Note that not all platforms support all data types. As such, comparing across platforms should only look at the common data types. victorvianna@google.com Services>Sync Time spent configuring data types for {ConfigurationType}. Recorded when DataTypeManagerImpl finishes. eliaskh@chromium.org rushans@google.com Services>Sync Histogram that keeps track of the bootstrap of Public-private key initialization outcome. Recorded upon attempt to commit NigoriSpecifics with CrossUserSharingPrivateKey, that happens upon browser restart. mmoskvitin@google.com treib@chromium.org Services>Sync Key derivation method used for sync custom passphrase on successful decryption of pending keys, i.e. when a passphrase is requested and the user types in the correct one. "Not set" will never be reported for this metric, since we always have an explicit key derivation method on successful decryption. mmoskvitin@google.com treib@chromium.org Services>Sync State of the derivation method used for sync custom passphrase on startup. Reported only when the passphrase type is CUSTOM_PASSPHRASE. mmoskvitin@google.com treib@chromium.org Services>Sync Time taken to derive keys in Nigori using a given key derivation method. This histogram is always recorded with one of the key derivation method suffixes. mastiz@chromium.org treib@chromium.org Services>Sync Breakdown of sync users whose cryptographer has pending keys. mmoskvitin@google.com mastiz@chromium.org Services>Sync Breakdown of sync users whose cryptographer is fully ready for encryption and decryption (initialized and no pending keys). mmoskvitin@google.com treib@chromium.org Services>Sync For users who have *not* selected the "Sync Everything" option, this records all the OS data types they have selected to sync. Samples are taken every time the Sync data types are (re)configured, which typically happens during startup and when the user changes any Sync settings. treib@chromium.org mastiz@chromium.org Services>Sync For Sync-the-feature users who have *not* selected the "Sync Everything" option, this records all the data types they have selected to sync. Samples are taken every time the Sync data types are (re)configured, which typically happens during startup and when the user changes any Sync settings. NOTE: This does NOT include OS datatypes. Use Sync.CustomOSSync for those. See also "Sync.SelectedTypesInTransportMode" which is the corresponding histogram for Sync-transport users. rushans@google.com mastiz@chromium.org Services>Sync Histogram of the run failures for the different sync datatypes. These are failures that occur after startup while the datatype is syncing. This is one of the base sync health metrics. The Sync.ModelTypeStoreBackendError and Sync.ModelTypeErrorSite histograms may help diagnosing the problem. rushans@google.com mastiz@chromium.org Services>Sync Histogram of the startup failures for the different sync datatypes. These are failures that occur during startup before the data type is fully loaded. These errors are caused by failures in reading metadata (or data) from the DB or by another failure in interaction with the model. The Sync.ModelTypeStoreBackendError and Sync.ModelTypeErrorSite histograms may help diagnosing the problem. mastiz@chromium.org rushans@google.com chrome-metrics-team@google.com Services>Sync The largest number of active and concurrently syncing devices known to any profile. May be 0 when there are no signed in/syncing profiles open. Logged with every UMA log. ssid@chromium.org mastiz@chromium.org chrome-metrics-team@google.com Services>Sync The largest number of active and concurrently syncing devices of type {DeviceType} known to any profile. May be 0 when there are no signed in/syncing profiles open. Logged with every UMA log. rushans@google.com treib@chromium.org Services>Sync Recorded for each committed sync entity ({SyncModelType}) when encryption is enabled (e.g. custom passphrase, always encrypted data type). The value is whether the encryption succeeded. ankushkush@google.com treib@chromium.org Services>Sync Size of individual sync entities in bytes. Recorded right before an entity is committed to the server. rushans@google.com treib@chromium.org Services>Sync Records status of each attempt to retrieve the instance id token. Replaces FCMInvalidations.InitialTokenRetrievalStatus for Sync standalone invalidations. rushans@google.com treib@chromium.org Services>Sync Whether an incoming FCM message has been delivered to at least one listener. Recorded on each incoming FCM message for standalone Sync invalidations. rushans@google.com treib@chromium.org Services>Sync Records time required to obtain an FCM registration token for Sync invalidations. Recorded on successful token fetch excluding token validation requests (Sync.FCMInstanceIdTokenRetrievalStatus can be used to compare with token fetch failure count). treib@chromium.org mastiz@chromium.org Services>Sync Recorded when HistorySyncBridge encounters a database error. As a result, the bridge stops operating (and tracking metadata) for the rest of the runtime of Chrome. treib@chromium.org mastiz@chromium.org Services>Sync Recorded when HistorySyncBridge encounters an incoming entity that is invalid, i.e. that fails some validity check. Counts in this histogram should be compared to counts in the "Remote" buckets of Sync.ModelTypeEntityChange3.History. rushans@google.com treib@chromium.org Services>Sync An outcome of handling incoming sync invalidations, recorded for each incoming FCM message when sync engine is registered for invalidations. This metric shows only the number of incoming messages regardless of the number of invalidated data types. treib@chromium.org mastiz@chromium.org Services>Sync An approximate state of sync at profile startup. Logs a few reasons sync definitely wouldn't be able to start, or that it probably can start. A dashboard stop and clear will fall under "turned off and setup not completed". Only recorded for "regular" profiles, i.e. those in which Sync might actually start. This excludes incognito profiles, guest profiles, system profiles (used for the profile picker), lockscreen profiles, etc. mmoskvitin@google.com treib@chromium.org Services>Sync Histogram tracks the number of invalidations received per sync data type. rushans@google.com treib@chromium.org Services>Sync Records the time required for sync invalidations to be fully initialized. The metric is calculated against sync engine creation time (may be deferred from browser startup). This metric may be reported several times during browser session whenever SyncEngine is reset, e.g. when sync was disabled and re-enabled again. mastiz@chromium.org rushans@google.com Services>Sync Records different causes for BookmarkSpecifics to be deemed invalid. Issues are recorded upon verifying validity of specifics received from the server. mmoskvitin@google.com mastiz@chromium.org Services>Sync The reason for a failure decrypting the keystore Nigori. igorruvinov@chromium.org pastarmovj@chromium.org Services>Sync Tracks the number of times the local sync backend was enabled by the user. Recorded when the SyncService is created, i.e. during profile startup. igorruvinov@chromium.org pastarmovj@chromium.org Services>Sync Tracks the size of the local sync backend database file. Recorded every time the roaming profile file is written by the client. igorruvinov@chromium.org pastarmovj@chromium.org Services>Sync Error code describing failure to read persisted sync state from local file. Recorded when an error is encountered during opening or reading of the local sync state file. igorruvinov@chromium.org pastarmovj@chromium.org Services>Sync Tracks the number of times the Roaming profile cannot be retrieved. Recorded when the SyncService is created, i.e. during profile startup. rushans@google.com treib@chromium.org Services>Sync Records local changes happening during an ongoing remote incremental update. ankushkush@google.com treib@chromium.org Services>Sync Records the time taken for all data types to finish loading, initiated from ModelLoadManager::LoadModels(). ankushkush@google.com treib@chromium.org Services>Sync Recorded whenever a data type fails to complete loading, called from ModelLoadManager::LoadModels(), before the timeout. This type is ignored and the rest of types which have loaded are marked ready for configuration. This type would ultimately be stopped once gets out of MODEL_STARTING state. victorvianna@google.com mastiz@chromium.org Services>Sync Recorded on every GetUpdatesResponse if the data type is blocked because due to the existence of undecryptable updates sent by the server. This is *not* recorded for the cases where sync encryption is in a valid pending state, e.g. user hasn't entered their passphrase yet. mastiz@chromium.org treib@chromium.org Services>Sync Recorded when the model (including both data and metadata) for a given data type was cleared due to `WipeModelUponSyncDisabledBehavior::kOnceIfTrackingMetadata`. In practice, this happens only on iOS, when Chrome was just restored from an OS-level backup. As a denominator, look at e.g. `Sync.InitialState2`. rushans@google.com treib@chromium.org Services>Sync Recorded once per commit message after which the quota for the given data type is depleted. If the commit cycle contains 150 commit messages for a given data type and the quota has initially 100 tokens, the quota gets depleted after first 100 messages and this histogram gets recorded for all the remaining messages (i.e. ~50 times) for the data type. Quota is tracked (and this metric gets recorded) only for data types that can be committed via JS API of extensions. rushans@google.com treib@chromium.org Services>Sync Recorded once per local change that gets scheduled for committing with an extra long nudge delay. This happens if and only if the commit quota for this data type for this user is depleted. Quota is tracked (and this metric gets recorded) only for data types that can be committed via JS API of extensions. This metric is not very reliable as nudging for local changes happens via thread hopping and there is no guarantee whether a local change will nudge for commit _before_ or _after_ it actually gets committed. rushans@google.com mastiz@chromium.org Services>Sync Recorded once per activation of a(n) {StorageType} data type; the value is the duration of the setup (time from the start of the configuration of sync until the data type receives all its sync data and the data is ready for the user). This metric is used for monitoring general health of sync client-side code. rushans@google.com mastiz@chromium.org Services>Sync Counts the number of entries for each model type. The count is based on metadata entries for the type. Recorded after sync configuration. This metric is used for monitoring general health of sync client-side code. treib@chromium.org rushans@google.com Services>Sync Recorded once for every sync entity change (whenever it is commited to the server or updated from the server). This metric is used for monitoring general health of sync client-side code. Note: This is only recorded with a data type suffix. The base version is never recorded. mastiz@chromium.org treib@chromium.org Services>Sync Records whenever ClientTagBasedModelTypeProcessor finds entity metadata during ModelReadyToSync() but initial_sync_done is false. treib@chromium.org rushans@google.com Services>Sync Recorded whenever ClientTagBasedModelTypeProcessor triggers a data type failure (recorded for both Start and Run failures). It distinguishes call sites for triggering such failures. rushans@google.com mastiz@chromium.org Services>Sync Counts the number of incremental sync updates received by the processor, per datatype. Logged in the model thread prior to any filtering, and includes tombstones as well as regular updates. rushans@google.com mastiz@chromium.org Services>Sync Counts the number of initial sync updates received by the processor, per datatype. Logged in the model thread prior to any filtering. mastiz@chromium.org rushans@google.com Services>Sync Estimated memory usage by sync datatype in kilobytes. Recorded after sync configuration. This metric is used for monitoring general health of sync client-side code. mastiz@chromium.org treib@chromium.org Services>Sync Records whenever an orphan metadata is encountered by the ClientTagBasedModelTypeProcessor. treib@chromium.org rushans@google.com Services>Sync Records the LevelDB Status error code for ModelTypeStore {Operation} operations. Recorded when there is an error while communicating with the DB for any data type that uses the ModelTypeStore. This metric should be used together with Sync.DataType[Run|Start]Failures2 to figure out the root cause of the data type failure. victorvianna@google.com mastiz@chromium.org Services>Sync Records how long it took from the moment the first update encrypted with this key was received by ModelTypeWorker, to the moment where the key was available to the Cryptographer. The time is measured by the number of GetUpdates cycles performed by the worker *while* the Cryptographer didn't have pending keys (and thus the key should have been known in theory). This replaced Sync.ModelTypeTimeUntilEncryptionKeyFound which used to measure the same time in GetUpdatesResponse-s. victorvianna@google.com mastiz@chromium.org Services>Sync Records the number of entities dropped when the data type decided that a certain encryption key was lost and dropped all pending updates encrypted with it. Future updates encrypted with such key will also be ignored by the data type, but those are *not* counted in this metric. treib@chromium.org rushans@google.com Services>Sync Recorded whenever a remote update for a particular data type gets dropped for the following reason: {Reason}. rushans@google.com treib@chromium.org Services>Sync Time from browser startup required to reach up-to-date download status for {SyncModelType}. Recorded at most once per browser session if sync and the data type is enabled (in either transport or full-sync mode) and there are no errors. If the data type is waiting for updates for too long, it will be recorded in Sync.ModelTypeWaitingForUpdatesTimeoutReason. rushans@google.com treib@chromium.org Services>Sync Recorded the reason of waiting for updates whenever a data type waits for updates during browser startup for too long, and it hasn't reached up-to-date or error download status. Each data type can be recorded at most once per browser session. Recorded only if the data type (and the whole sync) is enabled and there are no errors. mastiz@chromium.org treib@chromium.org Services>Sync Freshness of the sync data per received sync entity update, excluding reflections. The time represents the clock difference from the model being modified (usually on another device) until the change is processing by this instance of the browser. The time is capped at 1 week. Beware of potential clock skew due to two clients being involved. rushans@google.com src/components/sync/OWNERS Services>Sync Recorded if commit of outgoing password sharing invitations fails with a datatype-specific error code returned from the server. Records the returned error. Sync.CommitResponse.OUTGOING_PASSWORD_SHARING_INVITATION can be used to compare with the total number of commit requests. treib@chromium.org mastiz@chromium.org Services>Sync The active sync passphrase type at sync startup. mmoskvitin@google.com mastiz@chromium.org Services>Sync Sync passphrase type collected at each metrics upload. mastiz@chromium.org mmoskvitin@google.com Services>Sync The active sync passphrase type when the client receives a NOT_MY_BIRTHDAY or ENCRYPTION_OBSOLETE event from the server. mamir@chromium.org mastiz@chromium.org Services>Sync Records whether password notes are set in password specifics proto or the backup field. Recorded when decrypting password entity update upon download from the sync server. ankushkush@google.com src/components/sync/OWNERS Services>Sync Logs the count of local passwords moved to the account store. This is logged when, upon a batch upload request, passwords have been moved to the account store. Note that passwords may not have been uploaded to the server yet. Upload happens as part of the regular commit process. shabdan@google.com rushans@google.com Services>Sync Number of acknowledged and dropped invalidations broken down by reason. Recorded during browser shutdown, after a sync cycle or on incoming invalidation. bjfong@google.com ckitagawa@chromium.org Services>Sync Records the result of whether the placeholder tab had its local session found, had its data resynced successfully, or remained unsynced. Recorded once for each placeholder tab during session restore. mastiz@chromium.org Services>Sync Number of network requests issued by sync to the sync server, grouped by content type. mastiz@chromium.org treib@chromium.org Services>Sync A sync error code received from the sync server as a result of a client-initiated request. Note that this excludes network errors (e.g. client offline) and HTTP errors. mastiz@chromium.org Services>Sync Time taken for a client-initiated request to be sent over the network and receive the response from the sync server. mastiz@chromium.org rushans@google.com Services>Sync Emitted per network Commit() request to the sync server and datatype. It helps estimate how much load each datatype puts on the server. Note that the sum across buckets does not represent the total number of requests sent to the server, since multiple datatypes can be grouped in a single request. See Sync.PostedClientToServerMessage for the total number of requests/messages. mastiz@chromium.org rushans@google.com Services>Sync Emitted per network GetUpdates() request to the sync server and datatype. It represents how much load each datatype puts on the server. Note that the sum across buckets does not represent the total number of requests sent to the server, since multiple datatypes can be grouped in a single request. See Sync.PostedClientToServerMessage for the total number of requests/messages. mastiz@chromium.org rushans@google.com Services>Sync Emitted per network GetUpdates() request to the sync server, it represents the reason for sending such GetUpdates() request. mastiz@chromium.org rushans@google.com Services>Sync Records different issues encountered when processing incremental bookmark updates from the sync server. rushans@google.com mastiz@chromium.org Services>Sync Records different issues encountered when processing remote bookmarks from the sync server during the initial merge procedure. mmoskvitin@google.com treib@chromium.org Services>Sync For every user event that is recorded, this histogram records the type of event (i.e. which of the "oneof event" entries in the UserEventSpecifics proto was set). rushans@google.com treib@chromium.org Services>Sync Recorded whenever the sync engine is restarted. The recorded value is the calling site of ResetEngine. treib@chromium.org mastiz@chromium.org Services>Sync For users in transport mode (i.e. without Sync-the-feature enabled), this records which data types they have selected. Samples are taken every time the Sync data types are (re)configured, which typically happens during startup and when the user changes any Sync settings. See also "Sync.SyncEverything2" and "Sync.CustomSync3" which are the corresponding histograms for Sync-the-feature users. rushans@google.com treib@chromium.org Services>Sync Counts the number of commit results while committing sharing message. mastiz@chromium.org rushans@google.com treib@chromium.org Services>Sync Records whether refresh tokens were already fully loaded during SyncService initialization (i.e. during browser/profile startup). mastiz@chromium.org rushans@google.com treib@chromium.org Services>Sync Records whether there was a signed-in user during SyncService initialization (i.e. during browser/profile startup), specifically in the case where the account info was NOT fully loaded yet (see Sync.Startup.AccountInfoFullyLoaded2). mastiz@chromium.org treib@chromium.org Services>Sync Recorded on browser startup if the SyncEngine initialization is deferred by a fixed (configurable) delay due to performance reasons. In some cases, a data type may force sync to start before the delay finishes, causing the recorded time to be smaller. This histogram records the time spent after the SyncServiceImpl *creation* but before the SyncEngine initialization. treib@chromium.org mastiz@chromium.org Services>Sync Tracks how sync was turned off. Logged every time sync is told to stop permanently by the user (e.g. it won't come back on by itself). ankushkush@google.com treib@chromium.org Services>Sync This is recorded everytime a syncable pref is changed locally. This does not include changes sent during the initial sync/merge. ankushkush@google.com treib@chromium.org Services>Sync During browser startup, if sync is enabled and initial data exists, this records the time until a SyncableService is ready to process changes (both locally and coming from the server). The value is the duration from when SyncableServiceBasedBridge was initialized to the time when SyncableService has started (this comprises of loading all data from disk and MergeDataAndStartSyncing()). victorvianna@google.com src/components/sync/OWNERS Services>Sync Records the availability status (local, sync or non-available) for favicons associated with synced history entries. Recorded when one of the following is displayed: entries in chrome://history that are known to be present in remote history data; all entries in chrome://history/syncedTabs; tabs from other devices in the 3 dots history menu (desktop); tabs from other devices in the android Recent Tabs UI. jlebel@chromium.org chrome-signin-team@google.com Services>Sync Enumeration of error conditions that displays an infobar to the user. iOS only. treib@chromium.org mastiz@chromium.org Services>Sync Boolean histogram for whether the "Sync Everything" option was selected by a Sync-the-feature user. Samples are taken every time the Sync data types are (re)configured, which typically happens during startup and when the user changes any Sync settings. mmoskvitin@google.com treib@chromium.org Services>Sync Analogous to Sync.SyncEverything2 for Chrome OS sync settings. Reflects whether the "Sync Everything" option was selected by the user for OS datatypes. Samples are taken every time the Sync data types are (re)configured, which typically happens during startup and when the user changes any Sync settings. rushans@google.com treib@chromium.org Services>Sync Counts the number of Sync stopped events broken down by whether it was reported to the server. The event may be reported only if an access token and a birthday are not empty. Recorded when sync engine is stopped or disabled (it doesn't include regular browser shutdown). rushans@google.com treib@chromium.org Services>Sync Counts of responses (both http code and net error code) for Sync stopped event URL fetches. Note that requests that timed out are not covered by this histogram; see Sync.SyncStoppedURLFetchTimedOut for that. rushans@google.com treib@chromium.org Services>Sync Whether a Sync stopped event URL fetch timed out or not. Note that this records true on timeout and false on success, but doesn't record anything if the fetch failed for any other reason. victorvianna@google.com src/components/sync/OWNERS Services>Sync Logged when the server instructs the client to throttle all its data types. See also Sync.ThrottledSomeModelTypes which records a different event. This histogram can help explain changes in Sync.PostedClientToServerMessageError2::THROTTLED. victorvianna@google.com src/components/sync/OWNERS Services>Sync Logged when the sync server instructs this client to throttle a special list of data types. See also Sync.ThrottledAllModelTypes which records a different event. This histogram can help explain changes in Sync.PostedClientToServerMessageError2::THROTTLED. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether access token fetching attempt was successful upon every request to Security Domains service. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether attempt of adding trusted vault keys was successful (i.e. whether pending keys state resolved). mmrashad@google.com mmoskvitin@google.com Services>Sync Records the known degraded recoverability value when the degraded recoverability handler is started. Note that the value reflects state restored from the file and recorded before sending new request to the server. mmoskvitin@google.com mastiz@chromium.org Services>Sync Simplified version of Sync.TrustedVaultDeviceRegistrationState. Records whether the local device is registered (and ignores whether re-registration was completed/pending/in-flight) upon startup (if signed in) or upon first signin. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records the outcome of device registration attempt upon request completion or failure. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether the local device is registered on the server upon startup (if signed in) or upon first signin, and if not registered, provides insights into why. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records the result of an attempt to download trusted vault keys from the server (includes all registration versions). mmoskvitin@google.com mastiz@chromium.org Services>Sync Records the result of an attempt to download trusted vault keys from the server, specifically if the local device is known to have a V1 registration. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether user action was required to fetch trusted vault keys upon first sync (i.e. after signin). Recorded only if trusted vault passphrase type is used and sync-the-feature is enabled. Recorded at most once per browser/profile lifetime. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether user action was required to fetch trusted vault keys upon startup. Recorded only if trusted vault passphrase type is used and at most once per browser/profile lifetime. {TrustedVaultTimeSinceMigrationSuffix} mmoskvitin@google.com mastiz@chromium.org Services>Sync Records number of trusted vault keys fetched upon fetching completion. mmoskvitin@google.com mastiz@chromium.org Services>Sync Recorded when fetching trusted vault keys is attempted. mmoskvitin@google.com mastiz@chromium.org Services>Sync Recorded when reading local trusted vault file. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether writing local trusted vault file upon each write. mmrashad@google.com mmoskvitin@google.com Services>Sync Recorded when an immediate degraded recoverability request is going to be sent to the server. Records which heuristic triggered immediate request of the current degraded recoverability state from the server. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether invocations to the Javascript API chrome.addTrustedSyncEncryptionRecoveryMethod(), when received via Mojo in the browser process, corresponds to an incognito profile. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether invocations to the Javascript API chrome.addTrustedSyncEncryptionRecoveryMethod() completed successfully. Instrumented on Android only. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether invocations to the Javascript API chrome.addTrustedSyncEncryptionRecoveryMethod() specify a user ID that is known by IdentityManager. Instrumented on Android only. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records invocations to the Javascript API chrome.addTrustedSyncEncryptionRecoveryMethod() and whether the passed arguments could be successfully parsed (which doesn't imply the function actually succeeded). mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether invocations to the Javascript API chrome.setSyncEncryptionKeys(), when received via Mojo in the browser process, corresponds to an incognito profile. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records invocations to the Javascript API chrome.setSyncEncryptionKeys() and whether the passed arguments could be successfully parsed (which doesn't imply the function actually succeeded). mmoskvitin@google.com mastiz@chromium.org Services>Sync Recorded when user clicks/taps on trusted vault error button for the keys-missing error state. Buckets represents the UI elements which contain trusted vault error button. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether local data was successfully decrypted upon every attempt to read local file. mmoskvitin@google.com mastiz@chromium.org Services>Sync Recorded when user clicks/taps on trusted vault error button for the recoverability-degraded error state. Buckets represents the UI elements which contain trusted vault error button. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records whether user action was required to improve the recoverability of trusted vault keys. Recorded only if trusted vault passphrase type is used, when keys are locally available and at most once per browser/profile lifetime. {TrustedVaultTimeSinceMigrationSuffix} mmrashad@google.com mmoskvitin@google.com Services>Sync Records the status of the degraded recoverability upon the request completion. Note that this is the status on the server side, which could be error if the request was failed. mmoskvitin@google.com mastiz@chromium.org Services>Sync Counts of responses (both http code and net error code) for requests to the Trusted Vault server (aka Security Domain Service). Note that requests that timed out are not covered by this histogram. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records the result of verifying the state of the local device registration, which is achieved by simulating a key-download procedure. Recorded only for already-registered devices (V0 or V1) that have a primary account set, 10 seconds after metric Sync.TrustedVaultDeviceRegistrationState is recorded. mmoskvitin@google.com mastiz@chromium.org Services>Sync Records the result of verifying the state of the local device registration, which is achieved by simulating a key-download procedure. Recorded only for V1-registered devices that have a primary account set, 10 seconds after metric Sync.TrustedVaultDeviceRegistrationState is recorded. mastiz@chromium.org Services>Sync Recorded when TypedURLSyncBridge encounters a database error. As a result, the bridge stops operating (and tracking metadata) for the rest of the runtime of Chrome. mastiz@chromium.org treib@chromium.org Services>Sync Counts of responses (both http code and net error code) for Sync URL fetches. Note that requests that timed out are not covered by this histogram; see Sync.URLFetchTimedOut for that. mastiz@chromium.org treib@chromium.org Services>Sync Whether a URL fetch timed out or not. Timing out implies the fetch was stalled for an unknown reason. Note that this records true on timeout and false on success, but doesn't record anything if the fetch failed for any other reason.