kristianm@chromium.org agl@chromium.org Collected on Windows at startup. Records status for various virtual TPM operations that Chrome artificially triggers on startup for measurement purposes. Note that if new key creation fails, wrapped key creation and message signing will not take place. kristianm@chromium.org wfh@chromium.org Collected on Windows at startup. Records status for various TPM operations that Chrome artificially triggers on startup for measurement purposes. Note that if new key creation fails, wrapped key creation and message signing will not take place. kristianm@chromium.org agl@chromium.org Error code returned by NCryptCreatePersistedKey. One of the error codes from https://learn.microsoft.com/en-us/windows/win32/com/com-error-codes-4. kristianm@chromium.org agl@chromium.org Error code returned by NCryptFinalizeKey. One of the error codes from https://learn.microsoft.com/en-us/windows/win32/com/com-error-codes-4. kristianm@chromium.org agl@chromium.org Error code returned by NCryptOpenKey. One of the error codes from https://learn.microsoft.com/en-us/windows/win32/com/com-error-codes-4. kristianm@chromium.org agl@chromium.org Error code returned by NCryptOpenStorageProvider. One of the error codes from https://learn.microsoft.com/en-us/windows/win32/com/com-error-codes-4. kristianm@chromium.org agl@chromium.org Collected on Windows at startup. Records status for various virtual TPM actions that Chrome artificially triggers on startup for measurement purposes. Note that if new key creation fails, wrapped key creation and message signing will not take place. kristianm@chromium.org wfh@chromium.org Collected on Windows at startup. Records status for various TPM actions that Chrome artificially triggers on startup for measurement purposes. Note that if new key creation fails, wrapped key creation and message signing will not take place. agl@chromium.org davidben@chromium.org wfh@chromium.org Collected on Windows at startup. Records whether a TPM is present and, if so, what the best supported algorithm is. kristianm@chromium.org agl@chromium.org Collected on Windows at startup. Records whether a virtual and/or hardware TPM is present. alexilin@chromium.org kristianm@chromium.org Records the time that passed between starting a TPM operation on an unexportable_keys::UnexportableKeyService and completing the operation (either successfully or not). This time includes both the time spent waiting in a task queue and the execution time. These sub-intervals are covered by Crypto.UnexportableKeys.BackgroundTaskQueueWaitDuration and Crypto.UnexportableKeys.BackgroundTaskRunDuration histograms correspondingly. Includes operations that were scheduled with {Priority}. Recorded right after a TPM operation completes. alexilin@chromium.org kristianm@chromium.org Records the time spent waiting in a task queue for the subset of TPM operations that are asynchronously scheduled through unexportable_keys::UnexportableKeyService. This duration is a sub-interval of Crypto.UnexportableKeys.BackgroundTaskDuration. Includes operations that were scheduled with {Priority}. Recorded right before a TPM operation is sent to the background thread for execution. alexilin@chromium.org kristianm@chromium.org Records the result of the subset of TPM operations that are scheduled asynchronously through unexportable_keys::UnexportableKeyService. In some error cases, the result might be returned synchronously. Recorded right after a TPM operation completes. Recorded only for {TaskType}. alexilin@chromium.org kristianm@chromium.org Records the time that passed between starting executing a TPM operation on a background thread and completing the operation (either successfully or not). Includes only a subset of TPM operations that are scheduled asynchronously through unexportable_keys::UnexportableKeyService. This duration is a sub-interval of Crypto.UnexportableKeys.BackgroundTaskDuration. Unlike Crypto.UnexportableKeys.BackgroundTaskDuration, this histogram is split by a task type instead of a task priority because the priority doesn't matter once a task starts executing. Only one task can be executed at the time due to TPM limitations. Includes {TaskType}. Recorded right after a TPM operation completes. kristianm@chromium.org agl@chromium.org Collected on Windows at startup. Records whether a virtual TPM is present and, if so, what the best supported algorithm is. morlovich@chromium.org yhirano@chromium.org For every http cache transaction with a pattern (see HttpCache.Pattern), the time from the first access to the disk cache until the transaction was done. bashi@chromium.org net-dev@chromium.org The time taken an HttpCache::Transaction to be added to ActiveEntry. It roughly captures time to acquire a write lock for an disk cache. Recorded every time a transaction (re)starts. Not recorded if the cache is memory-backed. morlovich@chromium.org yhirano@chromium.org For http cache transactions in which a network request was sent, the time elapsed between beginning the request and sending it over the network; this is the time spent accessing the disk cache. yhirano@chromium.org net-dev@chromium.org The time taken to create a disk cache entry. Recorded when the entry is created for the first time in the HttpCacheTransaction. Not recorded if the cache is memory-backed. bashi@chromium.org blink-network-stack@google.com Whether or not a response has `Cache-Control: no-store`. Recorded when a HTTP transaction is finished. This histogram is for {Type}. shivanisha@chromium.org jkarlin@chromium.org Max file size allowed to be cached in the http cache. This is logged at the time the backend is created. yhirano@chromium.org net-dev@chromium.org The time taken to open a disk cache entry. Recorded when the entry is created for the first time in the HttpCacheTransaction. Not recorded if the cache is memory-backed. morlovich@chromium.org jkarlin@chromium.org For each http cache transaction, the recorded pattern. bashi@chromium.org blink-network-stack@google.com For each HTTP cache transaction, record total time spent {AccessType} the disk cache. Recorded when a transaction finished. This histogram does not record partial requests. dschinazi@chromium.org src/net/OWNERS Breakdown of the locations when SetBrokenAlternateProtocol is called. dschinazi@chromium.org src/net/OWNERS Breakdown of how requests which could potentially make use of an alternate protocol use or don't use the protocol. dschinazi@chromium.org src/net/OWNERS Breakdown of how requests which could potentially make use of an alternate protocol use or don't use the protocol, for connections to Google servers. tbansal@chromium.org dschinazi@chromium.org src/net/OWNERS Positive net error codes that failed alternative protocol requests end with. Recorded only when an alternative job fails, and the main job succeeds. horo@chromium.org src/net/OWNERS Positive net error codes that failed alternative protocol requests end with. Recorded only when an DNS alpn H3 job fails, and the main job succeeds. dschinazi@chromium.org src/net/OWNERS Information about the AlternativeService used for each request. mattm@chromium.org davidben@chromium.org Recorded each time a platform certificate change notification occurs. (Note that on Linux and ChromeOS these events are generated by the Chrome Certificate Manager but there are no notifications for changes that occurred outside of Chrome, and on Windows there are no notifications at all.) This does not count internal changes like Chrome Root Store and CRLSet updates. martinkr@google.com Whether certificate validation was disabled for a set of public keys because the --ignore-certificate-errors-spki-list switch was set on startup. martinkr@google.com Whether certificate validation was disabled because the --ignore-certificate-errors switch was set on startup. estark@chromium.org This histogram is recorded every time Chrome successfully verifies a certificate that chains to a private root. A value of true indicates that the certificate contains the TLS Feature Extension, and false indicates that it doesn't. estark@chromium.org This histogram is recorded every time Chrome successfully verifies a certificate that chains to a private root and the certificate contains the TLS Feature Extension. A value of true indicates that the connection had an OCSP response stapled, and a value of false indicates that it did not. rsleevi@chromium.org The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust anchor encountered in a successfully-verified certificate chain, during an HTTP URL request. The associated root certificate can be looked up using https://crt.sh/?spkisha256= . rsleevi@chromium.org The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust anchor encountered in a successfully-verified certificate chain, during verification time. The associated root certificate can be looked up using https://crt.sh/?spkisha256= . rsleevi@chromium.org This histogram is recorded every time Chrome successfully validates a certificate, but cannot determine a public trust anchor from the verified chain. A value of true indicates that the trust anchor list is out of date, as the OS believes a public trust anchor is being used, but the built-in list does not know about this trust anchor, while a value of false indicates that a public trust anchor was not used, thus there is no evidence that the list is out of date. This histogram is temporary until the transition to a unified root store (in source), at which point, the OS store will no longer be consulted for known roots. estark@chromium.org trusty-transport@chromium.org The origin breakdown of Signed Certificate Timestamps (SCTs). Emitted once for every SCT when first validated, which means 0 or more times during every SSL connection establishment. estark@chromium.org rsleevi@chromium.org Breakdown of Signed Certificate Timestamps (SCTs) validation status. Emitted once for every SCT when first validated, which means 0 or more times during every SSL connection establishment. hchao@chromium.org mattm@chromium.org Time needed to initialize the Android platform Trust store when using the builtin certificate verifier on Android. Removed 2022-02. bcb@chromium.org rsleevi@chromium.org While parsing an RSASSA-PSS signature algorithm, whether any invalid parameters were encountered that currently are not enforced as parsing errors. mattm@chromium.org hchao@chromium.org When initializing the builtin certificate verifier on Mac using the DomainCacheFullCerts implementation of the system trust store integration, this records how long it took to query the Mac keychain and initialize the cache of intermediate certificates. Warning: this histogram was expired from 2023-04-09 to 2023-06-07(M116); data may be missing. mattm@chromium.org hchao@chromium.org When initializing the builtin certificate verifier on Mac using the DomainCacheFullCerts or KeychainCacheFullCerts implementation of the system trust store integration, this records the number of certificates that were included in the cache of intermediate certificates. mattm@chromium.org hchao@chromium.org When initializing the builtin certificate verifier on Mac using the DomainCacheFullCerts or KeychainCacheFullCerts implementation of the system trust store integration, this records the number of certificates found in the Mac keychain. mattm@chromium.org hchao@chromium.org When initializing the builtin certificate verifier on Mac using the KeychainCacheFullCerts implementation of the system trust store integration, this records the number of certificates found in the Mac keychain which had trust records marking them as either trusted or distrusted. mattm@chromium.org hchao@chromium.org When the builtin certificate verifier is used on Mac and the platform trusted certificates cache is initialized (or re-initialized if keychain trust settings changed), records how long it took to initialize all the trust domain caches. Only recorded by the DomainCacheFullCerts implementation, which may or may not be used depending on Finch trial parameters. mattm@chromium.org hchao@chromium.org When the builtin certificate verifier is used on Mac and the platform trusted certificates cache is initialized (or re-initialized if keychain trust settings changed), records the number of certificates read from the {Domain} trust domain. Only counts certificates that were successfully parsed. Only recorded by the DomainCacheFullCerts implementation, which may or may not be used depending on Finch trial parameters. Warning: this histogram was expired from 2023-04-09 to 2023-06-07(M116); data may be missing. mattm@chromium.org hchao@chromium.org When the builtin certificate verifier is used on Mac and the platform trusted certificates cache is initialized (or re-initialized if keychain trust settings changed), records how long it took to initialize both the trust cache and the intermediates cache. Only recorded by the DomainCacheFullCerts and KeychainCacheFullCerts implementations, which may or may not be used depending on Finch trial parameters. mattm@chromium.org rsleevi@chromium.org Whether Name normalization was used in successfully validated certificate chains, only recorded for chains ending in privately trusted roots. Suffixed by the CertVerifyProc implementation. mattm@chromium.org rsleevi@chromium.org When using the builtin cert verifier, records the number of iterations taken during path building for each attempted verification. mattm@chromium.org rsleevi@chromium.org The actual amount of time spent verifying a certificate using the underlying cryptographic APIs. Because parallel verifications for the same certificate may be coalesced, histograms such as Net.SSLCertVerificationTime may be skewed, due to later verifications taking less overall time. This records the overall time spent verifying the first job to capture initialization costs. rsleevi@chromium.org mattm@chromium.org The actual amount of time spent verifying a certificate using the underlying cryptographic APIs. Because parallel verifications for the same certificate may be coalesced, histograms such as Net.SSLCertVerificationTime may be skewed, due to later verifications taking less overall time. This records the overall time spent verifying a single request, regardless of how many parallel requests are being served by the verification. dschinazi@chromium.org src/net/OWNERS Application protocol used for main frame resources. Logged by the renderer only for request that accessed the network and have received response headers. dschinazi@chromium.org src/net/OWNERS Application protocol used for subresources (resources other than main frame). Logged by the renderer only for request that accessed the network and have received response headers. mef@chromium.org pauljensen@chromium.org For each CONTENT_DECODING_FAILED, record the filter that failed. nidhijaju@chromium.org blink-network-stack@google.com For each response stream, record the Content-Encoding type. If multiple encoding types are specified, this histogram only records the last one. Note: Compression Dictionary Transport headers (i.e. "sbr" for Shared Brotli) will be recorded as "Unknown" in this histogram. toyoshim@chromium.org src/services/network/OWNERS The distribution of CORS error types on preflight requests. This reports whenever CORS checks detect an error on a preflight request. The InvalidResponse case corresponds to net errors for which there was no CORS error, e.g. CONNECTION_REFUSED, NX_DOMAIN, etc. titouan@chromium.org clamy@chromium.org src/services/network/OWNERS The distribution of CORS error types on preflight requests which are treated as warnings. This reports whenever CORS checks detect an error on a preflight request without failing the whole original network request, due to being configured to ignore these failures. dschinazi@chromium.org src/net/OWNERS The number of broken alternative services loaded from the prefs file on startup. Alternative services allow an origin server to specify additional means of interacting with it on the network. A broken alternative service is one whose most recent connection attempt failed and whose retry timeout period has not yet expired. Recorded when broken alternative services are loaded from the prefs file on startup. dschinazi@chromium.org src/net/quic/OWNERS This counts the number of server configs persisted in prefs file. dschinazi@chromium.org src/net/OWNERS The number of recently broken alternative services loaded from the prefs file on startup. Alternative services allow an origin server to specify additional means of interacting with it on the network. A recently broken alternative service is one whose most recent connection attempt failed. Recorded when broken alternative services are loaded from the prefs file on startup. horo@chromium.org src/net/OWNERS Whether or not `prefs::kAdditionalDnsQueryTypesEnabled` is enabled. Recorded at startup if disabled or whenever Chrome is believed to be enterprise-managed (per the same detection as the default disabling of DoH). Measures whether or not enterprise admins are setting the disable, potentially due to issues encoutered with HTTPS/INTEGRITY query experiments. horo@chromium.org src/net/OWNERS Whether or not the DNS configuration read from a nsswitch.conf file is considered compatible with Chrome, that is that the configuration did not contain any options that Chrome is unable to support using the built-in resolver. Reported whenever a nsswitch.conf file is read by Chrome. horo@chromium.org src/net/OWNERS Counter enum recorded whenever `net::DnsConfigService` detects a change to the nsswitch.conf DNS configuration file. horo@chromium.org src/net/OWNERS Whether or not the "hosts:" database was found in an nsswitch.conf DNS configuration file. Reported whenever Chrome has successfully read the nsswitch.conf file and is beginning to attempt to parse it. horo@chromium.org src/net/OWNERS Enumeration of the nsswitch.conf service that caused a compatibility issue, leading to the nsswitch.conf DNS configuration being considered incompatible with Chrome. Only emitted when a specific token is present in the nsswitch.conf file, causing the incompatibility, e.g. because the service is always incompatible with Chrome or because the service is configured with incompatible actions. Deprecated 2022-20. As of M108, NIS is treated as incompatible. Instances where it was the cause of incompatibility will be recorded in Net.DNS.DnsConfig.Nsswitch.IncompatibleService. horo@chromium.org src/net/OWNERS Whether or not NIS service is registered in the "hosts:" database of an nsswitch.conf. Recorded when a resolv.conf file is successfully read by Chrome and the DNS configuration read from the resolv.conf file is considered compatible with Chrome. horo@chromium.org src/net/OWNERS Whether or not an attempt to read nsswitch.conf succeeded. May fail due to missing file or filesystem issues, but does not consider it a failure if the file is larger than the size limit (see Net.DNS.DnsConfig.Nsswitch.TooLarge for that case). Reported for all attempts to read nsswitch.conf. horo@chromium.org src/net/OWNERS Whether or not an attempt to read nsswitch.conf failed due to the file size being unreasonably large. Reported for all attempts to read nsswitch.conf. horo@chromium.org src/net/OWNERS Whether or not the DNS configuration read from a resolv.conf file is considered compatible with Chrome, that is that the configuration did not contain any options that Chrome is unable to support using the built-in resolver. Reported whenever a resolv.conf file is successfully read by Chrome. horo@chromium.org src/net/OWNERS Counter enum recorded whenever `net::DnsConfigService` detects a change to the resolv.conf DNS configuration file. horo@chromium.org src/net/OWNERS Whether or not an attempt to read resolv.conf succeeded and produced a `__res_state` struct for Chrome to attempt to use. Reported on all attempts to read the configuration. horo@chromium.org src/net/OWNERS Whether or not the DNS configuration read from a resolv.conf file is considered "valid", that is that it contains at least one DNS server. Reported whenever a resolv.conf file is successfully read by Chrome. horo@chromium.org src/net/dns/OWNERS Records details of the secure DNS mode used to configure the host resolver at construction of the network service. horo@chromium.org src/net/OWNERS Enumeration of whether or not the DNS configuration setting of Windows is considered compatible with Chrome and the reason why it is considered incompatible. Reported whenever the DNS configuration setting of Windows is read by Chrome. horo@chromium.org net-dev@chromium.org The number of hosts parsed from a Hosts file. Reported whenever a Hosts file is read and parsed. horo@chromium.org net-dev@chromium.org Estimated memory usage to keep the parsed result of a Hosts file. Reported whenever a Hosts file is read and parsed. horo@chromium.org net-dev@chromium.org The file size of a Hosts file. Reported whenever a Hosts file is read. awillia@chromium.org src/net/dns/OWNERS Status of HTTPS DNS records received as additional records in a DnsTask querying for HTTPS. This would represent a recurssive resolver that is HTTPS-aware and performing followup queries on behalf of the client. Recorded as DNS responses are parsed. awillia@chromium.org src/net/dns/OWNERS Status of HTTPS DNS records received as additional records in a DnsTask querying for a type other than HTTPS. Recorded as DNS responses are parsed. Removed in crrev.com/c/1355602. pauljensen@chromium.org mef@chromium.org Counts of specific error codes returned by DnsTask if a subsequent HostResolverSystemTask succeeded. horo@chromium.org src/net/OWNERS Duration of time taken by DnsTask (the grouping of all individual DNS queries for a single instance of resolving a name) in resolutions that succeeded. horo@chromium.org src/net/OWNERS Enumeration of whether or not an HTTPS (SVCB) record transaction succeeded and whether or not any failure is fatal to the DnsTask. Recorded for all completed HTTPS record transactions. horo@chromium.org src/net/OWNERS Enumeration of the logic path used (e.g. different protocols) for each started DnsAttempt (the representation of an individual network request to a DNS server). awillia@chromium.org src/net/dns/OWNERS Duration of time taken by an insecure DnsTransaction to fail. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by an insecure DnsTransaction to succeed. awillia@chromium.org src/net/dns/OWNERS Counts of specific error codes returned by secure DnsTransactions to a DoH server that is unavailable or has unknown availability. These transactions may be probe queries or queries issued in the secure DNS mode. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a secure DnsTransaction to a DoH server that is unavailable or has unknown availability to fail. These transactions may be probe queries or queries issued in the secure DNS mode. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a secure DnsTransaction to a DoH server that is unavailable or has unknown availability to succeed. These transactions may be probe queries or queries issued in the secure DNS mode. awillia@chromium.org src/net/dns/OWNERS Counts of specific error codes returned by secure DnsTransactions to an available DoH server. A DoH server is available if a probe has been successfully completed and fewer than a threshold amount of failures have occurred. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a secure DnsTransaction to an available DoH server to fail. A DoH server is available if a probe has been successfully completed and fewer than a threshold amount of failures have occurred. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a secure DnsTransaction to an available DoH server to succeed. A DoH server is available if a probe has been successfully completed and fewer than a threshold amount of failures have occurred. horo@chromium.org src/net/OWNERS Enumerated status of the reason why the built-in DNS resolver has detected a "low entropy" situation for DNS over UDP and has switched to DNS over TCP. Replaced by Net.DNS.H3SupportedGoogleHost.TaskTypeMetadataAvailability2 on 2022-12. horo@chromium.org src/net/OWNERS The succeeded DNS Task type of HostResolverManager::Job (the basic internal unit of work for non-local host resolutions, potentially merging redundant requests from Chrome) that succeeded with or without valid HTTPS DNS metadata. This is recorded when a DNS Job succeeded for a domain if the domain is one of Google hosts which that is expected to have valid HTTPS DNS metadata with HTTP/3 support. horo@chromium.org src/net/OWNERS The succeeded DNS Task type of HostResolverManager::Job (the basic internal unit of work for non-local host resolutions, potentially merging redundant requests from Chrome) that succeeded with or without valid HTTPS DNS metadata. This is recorded for successful https- or wss-schemed queries to a set of Google hosts expected to have HTTPS DNS metadata, if the query type requests the HTTPS record. horo@chromium.org davidben@chromium.org src/net/OWNERS Records which RCODE the DNS server specified when it responded to our HTTPS query. If the query timed out before getting a response, "TimedOut" is recorded instead of an RCODE value. Histograms are emitted at the completion of a DnsTask's final transaction. horo@chromium.org davidben@chromium.org src/net/OWNERS Indicates whether the result of an HTTPS query was validly parsable or mangled. Only recorded when DnsRcode indicates NoError. Histograms are emitted at the completion of a DnsTask's final transaction. horo@chromium.org davidben@chromium.org src/net/OWNERS Records true when we receive an HTTPS record and an error RCODE at the same time. Only recorded for true. Histograms are emitted at the completion of a DnsTask's final transaction. horo@chromium.org davidben@chromium.org src/net/OWNERS Records how many ms the DNS server took to respond to address queries. Histograms are emitted at the completion of a DnsTask's final transaction. horo@chromium.org davidben@chromium.org src/net/OWNERS Records how many ms the DNS server took to respond to an HTTPS query. Histograms are emitted at the completion of a DnsTask's final transaction. horo@chromium.org davidben@chromium.org src/net/OWNERS Records a ratio indicating the relative HTTPS query resolve time compared to the slower A or AAAA resolve time, where A/AAAA/HTTPS belong to the same DnsTask. Multiply this value by 10 to obtain a percentage P. The HTTPS query completed in roughly P% of the slower A/AAAA resolve time. Values smaller than 10 indicate that HTTPS query was faster than A/AAAA. Values larger than 10 indicate that the HTTPS query was slower than A/AAAA. Histograms are emitted at the completion of a DnsTask's final transaction. horo@chromium.org src/net/OWNERS Duration of time taken by an insecure DnsTask in resolutions that failed. horo@chromium.org net-dev@chromium.org The duration of time DnsTransactions spend waiting to be started by a DnsTask, aggregated by HostResolverManager::Job. This metric is only recorded when the Job failed. horo@chromium.org net-dev@chromium.org The duration of time a DnsTransaction spends waiting to be started by a DnsTask. The dominant factor is likely the time spent waiting for other DnsTransactions to complete, i.e. waiting for DnsTask::StartNextTransaction to be invoked by the dispatcher. If there were no limit on the number of concurrent DNS queries, we would expect this metric to be near zero. horo@chromium.org net-dev@chromium.org The duration of time DnsTransactions spend waiting to be started by a DnsTask, aggregated by HostResolverManager::Job. This metric is only recorded when the Job succeeded. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a probe attempt to fail. The time is measured since the probe sequence was initiated due to a DNS config change. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a probe attempt to succeed. The time is measured since the probe sequence was initiated due to a DNS config change. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a probe attempt to fail. The time is measured since the probe sequence was initiated due to a network change. awillia@chromium.org src/net/dns/OWNERS Duration of time taken by a probe attempt to succeed. The time is measured since the probe sequence was initiated due to a network change. horo@chromium.org src/net/OWNERS Duration of HostResolver requests from Start() until completion. Includes requests resolved synchronously using fast local sources, e.g. from cache, recorded as 0. Excludes speculative requests. horo@chromium.org src/net/OWNERS Duration of HostResolver requests from Start() until completion. Excludes speculative requests and requests resolved using fast local sources, e.g. from cache. horo@chromium.org src/net/OWNERS Whether a HostResolverManager::Job (the basic internal unit of work for non-local host resolutions, potentially merging redundant requests from Chrome) succeeded or failed, and whether it was speculative. awillia@chromium.org src/net/OWNERS The state of the Secure DNS (DoH) auto-upgrade functionality. This histogram is only emitted by clients with secure DNS set to automatic mode, and the emission occurs one minute after the insecure DNS to secure DNS auto-upgrade network probing begins. There will be one histogram emission per DoH provider in the system DNS configuration per NetworkContext that allows using secure DNS queries, and re-emissions can occur each time the DNS configuration changes. horo@chromium.org src/net/OWNERS For DNS resolutions that failed after less than 10 ms, which are probably local failures, what error code the jobs failed with. horo@chromium.org src/net/OWNERS For DNS resolutions that failed after at least 10 ms, which are probably remote failures or connectivity problems, what error code the jobs failed with. horo@chromium.org src/net/OWNERS Duration of time taken by HostResolverManager::Job (the basic internal unit of work for non-local host resolutions, potentially merging redundant requests from Chrome) in resolutions that failed. This is the time to resolve a hostname from start to finish. Excludes jobs where all requests are speculative. horo@chromium.org src/net/OWNERS Duration of time taken by HostResolverManager::Job (the basic internal unit of work for non-local host resolutions, potentially merging redundant requests from Chrome) in resolutions that succeeded. This is the time to resolve a hostname from start to finish. Excludes jobs where all requests are speculative. bashi@chromium.org chrome-network-stack@google.com Time difference between the first address record (A or AAAA) and HTTPS record were resolved. Recorded when an address record was resolved before HTTPS record and the address record was resolved {Bucket}. bashi@chromium.org chrome-network-stack@google.com Time difference between A and AAAA records were resolved. Recorded when {Variant}, and the first one was resolved {Bucket}. horo@chromium.org src/net/OWNERS Duration of time taken by HostResolverSystemTask (the grouping of all individual DNS queries for a single instance of resolving a name using the system resolver) in resolutions that failed. horo@chromium.org src/net/OWNERS Duration of time taken by HostResolverSystemTask (the grouping of all individual DNS queries for a single instance of resolving a name using the system resolver) in resolutions that succeeded. awillia@chromium.org src/net/dns/OWNERS Records the outcome of a DoH probe attempt on the first valid entry in the custom text field. awillia@chromium.org src/net/dns/OWNERS Records the outcome of a formatting validation attempt on the custom text field. horo@chromium.org src/net/dns/OWNERS True if upgrade to DoH from a DoT hostname was attempted and succeeded. False if it was attempted and failed. horo@chromium.org src/net/dns/OWNERS True if there was at least one public nameserver during an attempt to upgrade to DoH from insecure DNS. False if there were no public nameservers during an attempt to upgrade to DoH from insecure DNS. Warning: this histogram was expired from 2023-04-23 to 2023-06-12; data may be missing. horo@chromium.org src/net/dns/OWNERS True if upgrade to DoH was not attempted because the DoH config was already specified. False if upgrade to DoH was not attempted for some other reason. horo@chromium.org src/net/dns/OWNERS True if upgrade to DoH was not attempted because of unhandled options in the system config. False if upgrade to DoH was not attempted for some other reason. Emitted each time the DnsConfig is updated. horo@chromium.org src/net/dns/OWNERS True if upgrade to DoH from insecure DNS was attempted and succeeded. False if it was attempted and failed. mmenke@chromium.org The time measured before starting DNS lookup until after the connection is complete. ricea@chromium.org src/net/network_error_logging/OWNERS The outcome of a Domain Reliability beacon, logged upon destruction of the beacon. mmenke@chromium.org Positive net error codes that requests for pages end with, including net::OK and net::ERR_ABORTED. This only counts loads in "main frames" for https://www.google.com (it does not for example count the error codes for subresoures on a page). It excludes main frame navigations that are converted to downloads (unless they fail / are aborted before it's known that they would be a download), and requests handled externally (like mailto links). cmfcmf@chromium.org peletskyi@chromium.org Positive net error codes that HTTP requests using the isolated-app: URL scheme end with, including net::OK and net::ERR_ABORTED. mmenke@chromium.org Positive net error codes that requests for pages end with, including net::OK and net::ERR_ABORTED. This only counts loads in "main frames" (it does not for example count the error codes for subresoures on a page). It excludes main frame navigations that are converted to downloads (unless they fail / are aborted before it's known that they would be a download), and requests handled externally (like mailto links). mmenke@chromium.org Net error codes that requests for "subresources" end with, including net::OK and net::ERR_ABORTED. edwardjung@chromium.org src/net/OWNERS Counts of various events that can occur on the network error page. Note that this histogram enum buckets are not mutually exclusive and so a single error page load might report samples into multiple ones. Each bucket has descriptions that further explain the context of their samples. sclittle@chromium.org offline-dev@chromium.org Counts of the type of offline content suggestions clicked on the network error page. Reported upon click. sclittle@chromium.org offline-dev@chromium.org Counts of the type of offline content suggestions shown on the network error page. Multiple suggestions can be shown at the same time. Reported when the suggestions are presented. finnur@chromium.org alexbn@chromium.org Counts the number of times web apps receive `ERR_INTERNET_DISCONNECTED` and the alternative error page (rather than the dino) is shown. Reported when the error page html is being prepared. See `NetErrorHelper::GenerateLocalizedErrorPage` (crbug.com/1280518). yyanagisawa@chromium.org chrome-loading@google.com Records check points in the `BodyConsumerBase` class have been executed. This metrics is for investigating crbug.com/1431885. yyanagisawa@chromium.org chrome-loading@google.com Records check points in the `FetchManager::Loader` class have been executed. This metrics is for investigating crbug.com/1431885. Removed 2023-01. The workaround is now effectively disabled in Chromium (but not Cronet, as of writing), and the latest Chromium-side metrics report 0.00% of devices are still affected. davidben@chromium.org Records, on startup, for ARM devices running Android, whether the CPU is known to have a broken NEON unit. See https://crbug.com/341598. mpdenton@chromium.org src/net/OWNERS Per-authentication-scheme counts of HTTP authentication attempts and rejections. mmenke@chromium.org src/net/OWNERS Whether NTLMv2 was enabled for an authentication handshake. For a given data set the number of samples here is expected to be equivalent to the "NTLM Start" count in the "Net.HttpAuthCount" histogram. Note that NTLMv2 being enabled makes the client behavior equivalent to setting LmCompatibilityLevel to 3 or higher. meacer@chromium.org src/chrome/browser/ui/login/OWNERS Type of the HTTP auth prompt displayed. mpdenton@chromium.org src/net/OWNERS Per-authentication-scheme counts of HTTP authentication targets, such as secure servers or proxies. Emitted at the same time as Net.HttpAuthCount, on every HTTP authentication attempt or rejection. Please list the metric's owners. Add more owner tags as needed. Length of time that a received resource will be cacheable. bengr@chromium.org The difference between the size specified in the X-Original-Content-Length header and the size of the response body. Only includes resources that have the X-Original-Content-Length header. bengr@chromium.org 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. Replaces Net.HttpContentLength, recording non-DRP Http traffic as "Http.Direct" instead of "Http.Other". tsepez@chromium.org Count of requests which contained a basic auth username and password embedded in the URL itself. cfredric@chromium.org kaustubhag@chromium.org Counts the HTTP requests which involve reading from the cookie jar to construct a Cookie header vs. the HTTP requests which are disallowed from including a Cookie header. aakallam@chromium.org src/chrome/browser/ip_protection/OWNERS Total bytes sent over the network for an HttpJob request that is covered by IP Protection. These bytes will be recorded even if the IP Protection proxy is configured as `direct://` (i.e. an IP Protection proxy is configured but doesn't actually proxy any traffic). aakallam@chromium.org src/chrome/browser/ip_protection/OWNERS Total prefilter (e.g., before decompression) bytes read for an HttpJob request that is covered by IP Protection and served from the network. These bytes will be recorded even if the IP Protection proxy is configured as `direct://` (i.e. an IP Protection proxy is configured but doesn't actually proxy any traffic). djmitche@chromium.org src/chrome/browser/ip_protection/OWNERS Time it takes to complete an HttpJob that is covered by IP Protection, from starting the transaction until we are done reading, for jobs not served from the cache. This time will be recorded even if the IP Protection proxy is configured as `direct://` (i.e. an IP Protection proxy is configured but doesn't actually proxy any traffic). fayang@chromium.org src/net/quic/OWNERS Wait time of main job while there is an available SPDY session but no QUIC session. fayang@chromium.org src/net/quic/OWNERS Wait time of main job while there is no available SPDY session and no QUIC session. jkarlin@chromium.org shivanisha@chromium.org src/net/OWNERS Total prefilter (e.g., before decompression) bytes read for an HttpJob request. rch@chromium.org Scheme of the proxy server used by an HTTP job that failed, or SCHEME_DIRECT if not proxy was used. rch@chromium.org Scheme of the proxy server used by an HTTP job that succeeded, or SCHEME_DIRECT if not proxy was used. mmenke@chromium.org Time it takes to complete an HttpJob, from starting the transaction until we are done reading. davidben@chromium.org trusty-transport@chromium.org Time it takes to complete an HttpJob, from starting the transaction until we are done reading, if the response was received over TLS 1.3 and TCP. This is recorded to measure the impact of 0-RTT. davidben@chromium.org trusty-transport@chromium.org Time it takes to complete an HttpJob to a Google host, from starting the transaction until we are done reading, if the response was received over TLS 1.3 and TCP. This is recorded to measure the impact of 0-RTT. mmenke@chromium.org Time it takes to complete an HttpJob, from starting the transaction until we are done reading, for jobs served from the cache. mmenke@chromium.org Time it takes to complete an HttpJob, from starting the transaction until the job is killed. Note that we didn't detect the end of the data for this job. mmenke@chromium.org Time it takes to complete an HttpJob, from starting the transaction until we are done reading, for jobs not served from the cache. mmenke@chromium.org Time it takes to complete an HttpJob, from starting the transaction until we are done reading, for jobs when we read until no more data is available. bengr@chromium.org Net.HttpOriginalContentLength with non-data reduction proxy traffic properly labeled with the "Direct" suffix. 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. Replaces Net.HttpOriginalContentLength, breaking down traffic by Direct, ViaDRP, Bypassed, and Other. bengr@chromium.org Size specified in the X-Original-Content-Length header. Only includes resources that have the X-Original-Content-Length header. dschinazi@chromium.org tbansal@chromium.org src/net/OWNERS Time taken to establish the connection to the HTTP proxy. Note that the histogram expired briefly for M-86 and M-87 non-stable versions. Exact counts during that period may not be meaningful. ricea@chromium.org src/net/OWNERS The total number of headers for a net::HttpRequestHeaders object, recorded at destruction time. Because these objects are created and copied in many places and not necessarily sent over the network, this should not be considered an unbiased estimate of how many headers are sent in practice. The purpose of this histogram is to measure the appropriate amount of memory to allocate for headers when the object is created. See https://crbug.com/1477132. mmenke@chromium.org The count of HTTP Response codes encountered. mmenke@chromium.org src/net/OWNERS The total number of ServerInfo structs written to the network service's prefs file, recorded each time the HttpServerProperties are serialized to update the copy stored on disk. mmenke@chromium.org Time from when an HTTP request is issued to when the first byte is processed. davidben@chromium.org trusty-transport@chromium.org Time from when an HTTP request is issued to when the first byte is processed, if the response was not cached and received over TLS 1.3 and TCP. This is recorded to measure the impact of 0-RTT. davidben@chromium.org trusty-transport@chromium.org Time from when an HTTP request to a Google host is issued to when the first byte is processed, if the response was not cached and received over TLS 1.3 and TCP. This is recorded to measure the impact of 0-RTT. morlovich@chromium.org wicarr@microsoft.com webmedia@microsoft.com Records decision points on whether response-side media content will be cached or not. This is determined after receiving the HTTP response headers and before attempting to write the the cache. davidben@chromium.org src/third_party/boringssl/OWNERS Records, on startup, for ARM devices running Android, whether the kernel is missing AT_HWCAP2 from the ELF auxv and /proc/cpuinfo reports support for ARMv8 features. Those features should also be reported in AT_HWCAP2. This is to measure the workaround in https://crbug.com/boringssl/46. fbeaufort@chromium.org src/net/OWNERS The new network connection cost any time a change to the device's active default network is observed. dschinazi@chromium.org src/net/OWNERS The new network connection type any time a change to the device's active default network is observed. ksakamoto@chromium.org webpackage-dev@chromium.org When Network Error Logging observes a completed request of signed exchange that might generate a report, what happens to it. NEL observes all requests, both successful and unsuccessful. It sends reports for successful and unsuccessful requests at specified sampling rates so that error rates can be calculated. Insecure requests are discarded for having an insecure origin regardless of existence of a policy for the origin. horo@chromium.org src/net/OWNERS Log the reason when HttpNetworkTransaction retries. dschinazi@chromium.org src/net/quic/OWNERS The number of QUIC sessions when the QuicStreamFactory is destroyed. amanvr@chromium.org carlscab@chromium.org woa-performance@google.com Records the number of times OnTransferSizeUpdated is called from different overriding methods. This UMA is useful to understand the distribution of calls being made to this method and will help see the reductions in IPC when we implement a prototype (b/257057692) where we remove unnecessary URLLoaderClient::OnTransferSizeUpdated IPCs. dschinazi@chromium.org The time taken from requesting a PAC script to receiving the first byte of the response body on successful fetches. This does not include time spent doing proxy auto-discovery, or failed attempts at retrieving PAC scripts. If the response body was empty, this measures the total time to fetch the (empty) response body. dschinazi@chromium.org The time taken to successfully fetch a PAC script. This does not include time spent doing proxy auto-discovery, or failed attempts at retrieving PAC scripts. estark@chromium.org A validated certificate chain may be subject to additional pinning requirements on a per-domain basis. When pinning requirements are violated, Chrome attempts to send a report about the incident. This records the net error code when sending a pinning violation report fails. agl@chromium.org A validated certificate chain may be subject to additional "pinning" requirements on a per-domain basis. This records the fraction of successful matches between a certificate chain and a pin list. Removed 2023-05. bnc@chromium.org src/net/OWNERS Information about the value of the Vary response header in HTTP/2 pushed streams. dschinazi@chromium.org src/net/quic/OWNERS The number of active QUIC sessions before we activate a new QUIC session. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS Tracks the number of QUIC alt-svc advertisements parsed by Chrome in Google format vs in IETF format. renjietang@chromium.org src/net/OWNERS Log the connection error code when QUIC stream handle closes. renjietang@chromium.org src/net/OWNERS Log the net error code when QUIC stream handle closes. renjietang@chromium.org src/net/OWNERS Log the stream error code when QUIC stream handle closes. renjietang@chromium.org src/net/OWNERS Log success rate of processing trailing headers. renjietang@chromium.org src/net/quic/OWNERS The reason for the existing path validation when a new multi-port path creation is attempted but failed because of existing validation. renjietang@chromium.org src/net/quic/OWNERS The status of the multi-port path when the client initiates the migration. renjietang@chromium.org src/net/OWNERS When multi-port is enabled, log whether the server allows active migration that's required for multi-port wub@chromium.org src/net/quic/OWNERS The write result returned by the packet writer when the connection attempts to write a packet. dschinazi@chromium.org src/net/quic/OWNERS The number of active sessions that are degrading on network changes. The suffix specifies the network change. Emitted when there are more than one active sessions. The histogram is emitted when a network change happens which could affect the current default network, which includes the default network being changed, alternate networks being connected. It, however, doesn't emit when disconnecting an alternate network because that does not affect the current default network. dschinazi@chromium.org src/net/quic/OWNERS The number of active QUIC sessions when a network change is detected. The suffix specifies the network change. The histogram is emitted when a network change happens which could affect the current default network, which includes the default network being changed, alternate networks being connected. It, however, doesn't emit when disconnecting an alternate network because that does not affect the current default network. dschinazi@chromium.org src/net/quic/OWNERS The number of all sessions that detectes path degradation until a network change happens, including both active sessions and closed sessions. The suffix specifies the network change. The histogram is emitted when a network change happens which could affect the current default network, which includes the default network being changed, alternate networks being connected. It, however, doesn't emit when disconnecting an alternate network because that does not affect the current default network. dschinazi@chromium.org src/net/quic/OWNERS The total number of sessions that reports path degradation before a network change happens, including both still active sessions and closed sessions. The histogram is emitted when a network change happens which could affect the current default network, which includes the default network being changed, alternate networks being connected. It, however, doesn't emit when disconnecting an alternate network because that does not affect the current default network. dschinazi@chromium.org src/net/quic/OWNERS The number of total sessions that has been tracked since the first speculative error, including both active and closed sessions. Only recorded if non-zero. The histogram is emitted when a network change happens which could affect the current default network, which includes the default network being changed, alternate networks being connected. It, however, doesn't emit when disconnecting an alternate network because that does not affect the current default network. dschinazi@chromium.org src/net/quic/OWNERS The number of total sessions that has been closed due to QUIC_PACKET_WRITE_ERROR before first path degradation detection. The histogram is emitted when session path degrading is detected for the first time on the current network and there was a session closed with a speculative signal (QUIC_PACKET_WRITE_ERROR). dschinazi@chromium.org src/net/quic/OWNERS The percentage of active sessions that are degrading on network changes. The suffix specifies the network change. Emitted when there are at least two active sessions. The histogram is emitted when a network change happens which could affect the current default network, which includes the default network being changed, alternate networks being connected. It, however, doesn't emit when disconnecting an alternate network because that does not affect the current default network. dschinazi@chromium.org src/net/quic/OWNERS The percentage of all sessions that detectes path degradation until a network change happens, including both active sessions and closed sessions. Always emit 0 when there is no session reporting path degrading to speculate a connectivity failure on the current network. The suffix specifies the network change. The histogram is emitted when a network change happens which could affect the current default network, which includes the default network being changed, alternate networks being connected. It, however, doesn't emit when disconnecting an alternate network because that does not affect the current default network. dschinazi@chromium.org src/net/quic/OWNERS When a packet write error is detected by the session, if path degradation has been detected already on the same session. The histogram is emitted when a session encounters a QUIC_PACKET_WRITE_ERROR and is soon to be closed. dschinazi@chromium.org src/net/quic/OWNERS Tracks failure reasons to read/load/write of QuicServerInfo to and from disk cache. dschinazi@chromium.org src/net/quic/OWNERS The reason a QUIC packet could not be processed, logged for each dropped packet. dschinazi@chromium.org src/net/quic/OWNERS The number of QUIC packets received by a QUIC connection whose handshake was not confirmed when that connection is closed. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS The state of a QUIC connection's crypto hanshake as it progresses from starting to confirmation or failure. renjietang@chromium.org src/net/quic/OWNERS Log the success rate of HTTP layer reading QUIC response headers, for investigating b/177893733. bnc@chromium.org src/net/quic/OWNERS Stream error of QuicSpdyStream when QuicHttpStream::ComputeResponseStatus() returns ERR_QUIC_PROTOCOL_ERROR, for investigating b/177893733. renjietang@chromium.org src/net/quic/OWNERS The percentage comparison between alternative port probe failure when default path is degrading and in general. renjietang@chromium.org src/net/quic/OWNERS The percentage comparison between alternative port response time when default path is degrading and response time in general. Replaced by Net.QuicSession.NumDefaultPathDegrading in May 2023, as num_path_degrading is no longer specific to the multi-port feature. renjietang@chromium.org src/net/quic/OWNERS The number of time that a session which has multi-port enabled enters path-degrading state on the default path. renjietang@chromium.org src/net/quic/OWNERS The number of alternative port probing failure when the default path is degrading. renjietang@chromium.org src/net/quic/OWNERS The number of alternative port probing failure when the default path is healthy. dschinazi@chromium.org src/net/quic/OWNERS Time from when QUIC detects performance degradation on the current network to when QUIC notices a new network is connected. dschinazi@chromium.org src/net/quic/OWNERS Time from when QUIC detects performance degradation on the current network to when QUIC notices the current network is disconnected. dschinazi@chromium.org src/net/quic/OWNERS The time from QUIC detecting network performance degradation to an alternative network becoming default. dschinazi@chromium.org src/net/quic/OWNERS The time from network disconnection to an alternative network becoming default. dschinazi@chromium.org src/net/quic/OWNERS The number of times ServerConfigUpdateMessages ignored. horo@chromium.org src/net/OWNERS Log the retry delay caused by ERR_QUIC_PROTOCOL_ERROR. Recorded when HttpNetworkTransaction finishes. horo@chromium.org src/net/OWNERS The status of how HttpNetworkTransaction handles a ERR_QUIC_PROTOCOL_ERROR. Recorded when HttpNetworkTransaction finishes. horo@chromium.org src/net/OWNERS Log the QUIC error code when HttpNetworkTransaction handles a ERR_QUIC_PROTOCOL_ERROR. horo@chromium.org src/net/OWNERS Log the QUIC stream error code when HttpNetworkTransaction handles a ERR_QUIC_PROTOCOL_ERROR. dschinazi@chromium.org src/net/quic/OWNERS The state of the QUIC server information when it's loaded from the disk cache. dschinazi@chromium.org src/net/quic/OWNERS The number of pending stream requests aborted when the session is closed. Pending streams are those which could not be created immediately because there were too many active streams. bnc@chromium.org src/net/OWNERS Records whether the QUIC session received an Accept-CH entry for the given origin, which GetAcceptChViaAlps() returns. Logged every time QuicHttpStream::GetAcceptChViaAlps() is called, typically once for each request that is served over HTTP/3. bnc@chromium.org src/net/OWNERS Records both whether there are any valid origin fields and whether there are any invalid ones in the ACCEPT_CH frame. Logged during the TLS handshake of a QUIC connection if ALPS is negotiated, once for every ACCEPT_CH HTTP/3 frame received (possibly zero, typically not more than one). renjietang@chromium.org src/net/quic/OWNERS The number of active streams when the quic session decides to go away on path degrading. dschinazi@chromium.org src/net/quic/OWNERS True if the result of reading a packet from the network was ERR_IO_PENDING. Recorded for each packet when Read() returns. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS The number of BLOCKED frames recevied by a QuicSession when the session is closed. dschinazi@chromium.org src/net/quic/OWNERS The number of BLOCKED frames sent by a QuicSession when the session is closed. dschinazi@chromium.org src/net/quic/OWNERS The network error code returned to a QUIC session from the CertVerifier when a certification verification is attempted. dschinazi@chromium.org src/net/quic/OWNERS Time spent verifying a certificate when racing cert veriifcation with host resolution. dschinazi@chromium.org src/net/quic/OWNERS The final maximum packet size of the connection used by the client before the session is closed. dschinazi@chromium.org src/net/quic/OWNERS The network error code which resulted in all sessions being closed. wub@chromium.org src/net/quic/OWNERS For a QUIC session that is closed by a public reset, where the handshake was {HandshakeType}, this boolean shows whether it is a public reset sent from a Google server or not. wub@chromium.org fayang@chromium.org src/net/quic/OWNERS For a QUIC session that is closed by QUIC_TOO_MANY_RTOS at client, this is the number of packets it received before it is closed. wub@chromium.org fayang@chromium.org src/net/quic/OWNERS For a QUIC session that is closed by QUIC_TOO_MANY_RTOS at client, this is the number of packets it sent before it is closed. dschinazi@chromium.org src/net/quic/OWNERS True if the QUIC session is closed during the call to InitializeSession, logged for each session just after InitializeSession is called. dschinazi@chromium.org src/net/quic/OWNERS The network error code which resulted in the session being closed. renjietang@chromium.org src/net/quic/OWNERS When a new stream frame is added to a QUIC packet, record whether it's coalesced with the existing stream frames. dschinazi@chromium.org src/net/quic/OWNERS Samples of the number of round-trips needed by a QUIC connection before a request could be sent by the client. dschinazi@chromium.org src/net/quic/OWNERS True if a QUIC connection connected successfully after having been broken. Only emitted after a QUIC connection attempt to a server that was previous marked as broken. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error which caused a QUIC connection to be closed before the hanshake was confirmed, in the case where no packets were received. This provides a breakdown of the entires in Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value is BLACK_HOLE. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error which caused a QUIC connection to be closed before the hanshake was confirmed, in the case where at least 1 packet was received. This provides a breakdown of the entires in Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value is UNKNOWN. dschinazi@chromium.org src/net/quic/OWNERS The reason a QUIC handshake failed. dschinazi@chromium.org src/net/quic/OWNERS The number of streams open when a QUIC session crypto handshake timed out. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS The number of streams open when a QUIC session timed out. dschinazi@chromium.org src/net/quic/OWNERS The number of total streams created when a QUIC session crypto handshake timed out. dschinazi@chromium.org src/net/quic/OWNERS The QUIC application transport error code in a CONNECTION_CLOSE frame received from the server{GQuicMissing}. This is recorded for connections made to {ServerType}{HandshakeType}. davidben@chromium.org dschinazi@chromium.org src/net/quic/OWNERS dschinazi@chromium.org src/net/quic/OWNERS The QUIC transport error code in a CONNECTION_CLOSE frame received from the server{GQuicMissing}. This is recorded for connections made to {ServerType}{HandshakeType}. Warning: the ConnectionCloseErrorCodeServerIetfTransportGoogle variant was expired from 09/12/2022 to 03/22/2023; data may be missing. davidben@chromium.org dschinazi@chromium.org src/net/quic/OWNERS dschinazi@chromium.org src/net/quic/OWNERS The QUIC error code which resulted in the QUIC connection being closed by the {Closer}. This is recorded for connections made to {ServerType}{HandshakeType}. davidben@chromium.org dschinazi@chromium.org src/net/quic/OWNERS renjietang@chromium.org src/net/quic/OWNERS The duration of a QUIC connection starting from 1-RTT key available to connection close. fayang@chromium.org src/net/quic/OWNERS Duration of connections received PUBLIC_RESET. dschinazi@chromium.org src/net/quic/OWNERS Whether QUIC session's connection is flow control blocked when a PING message is sent to server. renjietang@chromium.org src/net/quic/OWNERS True if an active session already exists for a given Ip during connection. dschinazi@chromium.org src/net/quic/OWNERS The result of a QUIC connection migration attempt. The suffix specifies the cause of connection migration. dschinazi@chromium.org src/net/quic/OWNERS The IP Address family of this connection, as reported by the server. dschinazi@chromium.org src/net/quic/OWNERS The IP Address family of this connection, as seen locally. dschinazi@chromium.org src/net/quic/OWNERS Samples of the number of round-trips needed by a QUIC connection before a request could be sent by the client, when handshake confirmation was required. (The operating system randomly selected a source port for the connection.) dschinazi@chromium.org src/net/quic/OWNERS Count of errors during attempts to create a QUIC session (before even using the session). fayang@chromium.org src/net/quic/OWNERS Times of retransmission time out of connections with successful handshake. fayang@chromium.org src/net/quic/OWNERS Times of crypto retransmission timeout of connections with failed handshake. renjietang@chromium.org src/net/quic/OWNERS The number of draining streams when the quic session decides to go away on path degrading. dschinazi@chromium.org src/net/quic/OWNERS The number of duplicate packets recevied by a QuicSession when the session is closed. fayang@chromium.org src/net/quic/OWNERS The elapsed time between starting the crypto handshake and installing the first encryption key that can carry application data (either 0-RTT or 1-RTT). dschinazi@chromium.org src/net/quic/OWNERS The value of the TCP cubic sender's CWND when the session is closed. dschinazi@chromium.org src/net/quic/OWNERS Logged every time we parse a QUIC Finch config, and logs whether the config was valid. Invalid configs are most likely to be obsolete configs. Note that this is still logged (as true) when no variations config is present. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS Triggered any time Finch configures an obsolete QUIC version. Only recorded when obsolete versions are not allowed (which is the default). dschinazi@chromium.org src/net/quic/OWNERS This measures the time gap between the most recent write error and the network disconnection. dschinazi@chromium.org src/net/quic/OWNERS Whether QuicGoAwayFrame is received from server for connection migration due to client's port change. Logged when a QuicGoAwayFrame with error code QUIC_ERROR_MIGRATING_PORT is received. dschinazi@chromium.org src/net/quic/OWNERS The elapsed time between starting the crypto handshake, and receiving confirmation from the server. davidben@chromium.org dschinazi@chromium.org src/net/quic/OWNERS The elapsed time between starting the crypto handshake, and receiving confirmation from the server, measured only for ECH-capable servers. dschinazi@chromium.org src/net/quic/OWNERS The handshake status when the session attempts to migrate the connection according to different migration causes. fayang@chromium.org src/net/quic/OWNERS The handshake status when the session attempts to validate received server preferred address. dschinazi@chromium.org src/net/quic/OWNERS The handshake status when the session attempts to port migration on path degrading. dschinazi@chromium.org src/net/quic/OWNERS Whether path degrading has been detected by the time a QUIC connection is closed due to handshake timeout. dschinazi@chromium.org src/net/quic/OWNERS Header compression ratio as percentage for received headers using HPACK. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS Header compression ratio as percentage for sent headers using HPACK. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS Header compression ratio as percentage for received headers using QPACK. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS Header compression ratio as percentage for sent headers using QPACK. dschinazi@chromium.org src/net/quic/OWNERS The elapsed time between the end of resolving the DNS name of the server for a QUIC connection, and receiving crypto handshake confirmation from the server. Logged after crypto handshake is confirmed. dschinazi@chromium.org src/net/quic/OWNERS The number packets recevied by a QuicSession with an incorrect connection id when the sesesion is closed. dschinazi@chromium.org src/net/quic/OWNERS The source for the initial RTT estimate recorded when a QUIC session is created. dschinazi@chromium.org src/net/quic/OWNERS The number of key updates processed per connection, recorded on connection close. Only logged for connections which reached the 1-RTT level and supported key update. dschinazi@chromium.org src/net/quic/OWNERS Count of packets received that appeared to attempt a key update but failed decryption which have been received since the last successfully decrypted packet, recorded on connection close. Only logged for connections which reached the 1-RTT level and supported key update. mattm@chromium.org src/net/quic/OWNERS The reason why each key update occured. mattm@chromium.org src/net/quic/OWNERS Records the success or failure of the last key update for connections where the key update was initiated by the {Group} side. Failure is defined as having sent at least one packet in the new key phase but never receiving an ack for any packet sent in the new key phase before the connection was closed. fayang@chromium.org src/net/quic/OWNERS Time from handshake completion to last packet was sent for connections received PUBLIC_RESET. fayang@chromium.org src/net/quic/OWNERS A bitfield representing the last sent packet content before connection receives PUBLIC_RESET. fayang@chromium.org src/net/quic/OWNERS Max consecutive retransmission timeout before making forward progress. fayang@chromium.org src/net/quic/OWNERS Max consecutive retransmission timeout before making forward progress when blackhole has been detected. dschinazi@chromium.org src/net/quic/OWNERS The maximum packet sequence number reordering observed by a QUIC connection. dschinazi@chromium.org src/net/quic/OWNERS The ratio of the maximum reordering time of a QUIC packet to the min rtt. dschinazi@chromium.org src/net/quic/OWNERS The ratio of the maximum reordering time of a QUIC packet to the min rtt, only for those sessions with a min rtt larger than 100 ms. renjietang@chromium.org src/net/quic/OWNERS Records whether the migration of the QuicSession to a new socket is successful. dschinazi@chromium.org src/net/quic/OWNERS The minimum RTT observed during the life of a QUIC connection. dschinazi@chromium.org src/net/quic/OWNERS The number of MTU probes sent by the client during the session. Logged when the connection is destroyed. renjietang@chromium.org src/net/quic/OWNERS The number of active streams when idle timeout is detected and connection is being closed. renjietang@chromium.org src/net/quic/OWNERS The number of times that a session enters path-degrading state on the default path. renjietang@chromium.org src/net/quic/OWNERS The number of times that a session makes forward progress after the original default path is degrading. renjietang@chromium.org src/net/quic/OWNERS The number of successful migrations for a QUIC session. dschinazi@chromium.org src/net/quic/OWNERS Number of connection migrations exercised before the connection receives a public reset. dschinazi@chromium.org src/net/quic/OWNERS The number of QUIC streams opened when a new QUIC stream is created. dschinazi@chromium.org src/net/quic/OWNERS The number of pending stream requests when a new stream request is added to the pending list. Pending streams are those which could not be created immediately because there were too many active streams. renjietang@chromium.org src/net/quic/OWNERS The number of pings a QUIC connection sends during its lifetime. renjietang@chromium.org src/net/quic/OWNERS The number of streams waiting to write when idle timeout is detected and connection is being closed. dschinazi@chromium.org src/net/quic/OWNERS The total number of streams created by the client when the session is closed. fayang@chromium.org src/net/quic/OWNERS The result of a QUIC server preferred address migration attempt. dschinazi@chromium.org src/net/quic/OWNERS The number of missing packets between the current received packet and the previously largest received packet sequence number, when the current received packet had a lower sequence number than the previously received packet sequence number. dschinazi@chromium.org src/net/quic/OWNERS The number of times the current received packet had a lower sequence number than the previously received packet sequence number, and the size of the current packet is larger than the size of the previous packet. dschinazi@chromium.org src/net/quic/OWNERS The number of times the current received packet had a lower sequence number than the previously received packet sequence number. dschinazi@chromium.org src/net/quic/OWNERS The number of missing packets between the current received packet and the previously largest received packet sequence number. dschinazi@chromium.org src/net/quic/OWNERS The number of missing packets between the last received packet before a PING frame sent and the first packet received after PING sent. dschinazi@chromium.org src/net/quic/OWNERS The number of missing packets between the current received packet and the previously largest received packet sequence number, as reported by the remote end of the connection. dschinazi@chromium.org src/net/quic/OWNERS The ratio of the number of missing packets, to the maximum packet sequence number received, for QUIC connections longer than 21 packets received via dschinazi@chromium.org src/net/quic/OWNERS The number of packets retransmitted per 1000. Only sessions with packets_sent >= 100 are included. Recorded in session destructor. dschinazi@chromium.org src/net/quic/OWNERS The time taken to Write() a QUIC packet to the socket. Recorded for each packet when it is sent. The suffix specifies if the write completed synchonously or asynchronously. renjietang@chromium.org src/net/quic/OWNERS The result of path validation according to different migration causes. dschinazi@chromium.org src/net/quic/OWNERS The wait time of the pending stream when it is finally serviced. Pending streams are those which could not be created immediately because there were too many active streams. dschinazi@chromium.org src/net/quic/OWNERS The platform notification received by QUIC when network change happens. dschinazi@chromium.org src/net/quic/OWNERS The result of a QUIC port migration attempt. dschinazi@chromium.org src/net/quic/OWNERS True if the QUIC session prefers to use AES GCM because of hardware support. dschinazi@chromium.org src/net/quic/OWNERS Number of retries to send connectivity probing packet on new path until success. dschinazi@chromium.org src/net/quic/OWNERS The wait time to receive a matched probing response to mark connectivity probing as successful. Removed 2023-06. dschinazi@chromium.org src/net/quic/OWNERS The number of push streams received when the session is closed. Removed 2023-06. dschinazi@chromium.org src/net/quic/OWNERS The number of pushed and used streams when the session is closed. Removed 2023-06. dschinazi@chromium.org src/net/quic/OWNERS The number of bytes that is pushed but not used when the session is closed. Removed 2023-06. dschinazi@chromium.org src/net/quic/OWNERS The number of bytes that is pushed when the session is closed. dschinazi@chromium.org src/net/quic/OWNERS The ordinality of a header list within a connection during the encoding of which unacknowledged dynamic table entries could not be referenced due to the limit on the number of blocked streams. dschinazi@chromium.org src/net/quic/OWNERS The ordinality of a header list within a connection during the encoding of which at least one dynamic table insertion was blocked. dschinazi@chromium.org src/net/quic/OWNERS The ordinality of a header list within a connection during the encoding of which no dynamic table insertion was blocked. dschinazi@chromium.org src/net/quic/OWNERS The ordinality of a header list within a connection during the encoding of which the limit on the number of blocked streams did not prevent referencing unacknowledged dynamic table entries. dschinazi@chromium.org src/net/quic/OWNERS Version of the QUIC protocol used for this connection. dschinazi@chromium.org src/net/quic/OWNERS The network error code returned when attempting to read from a QUIC connection. The suffix specifies the condition/source of the read error. dschinazi@chromium.org src/net/quic/OWNERS The network error code returned when attempting to read on the current network from a QUIC connection after handshake has been confirmed. dschinazi@chromium.org src/net/quic/OWNERS The value of the SETTINGS_QPACK_BLOCKED_STREAMS parameter received on an HTTP/3 connection, if any. dschinazi@chromium.org src/net/quic/OWNERS The number of SETTINGS parameters received on an HTTP/3 connection, incremented by one (the SETTINGS frame can be empty). momoka@google.com ricea@chromium.org src/net/quic/OWNERS The value of the SETTINGS_ENABLE_CONNECT_PROTOCOL parameter received on an HTTP/3 connection, if the parameter is not present log false. dschinazi@chromium.org src/net/quic/OWNERS The value of the SETTINGS_MAX_HEADER_LIST_SIZE parameter received on an HTTP/3 connection, if any. dschinazi@chromium.org src/net/quic/OWNERS The value of the SETTINGS_QPACK_MAX_TABLE_CAPACITY parameter received on an HTTP/3 connection, if any. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS The number of reserved SETTINGS parameters (that is, with identifier in the form 0x1f * N + 0x21 for a non-negative integer value of N) received on an HTTP/3 connection, incremented by one (there might be zero reserved identifiers). Defined at https://quicwg.org/base-drafts/draft-ietf-quic-http.html#name-defined-settings-parameters. These should not be treated specially on the receive side, because they are sent to exercise the requirement that unknown identifiers are ignored. Here an exception is made for logging only, to understand what kind of identifiers are received. dschinazi@chromium.org src/net/quic/OWNERS True if the QUIC REJ message received from the server contains a proof. dschinazi@chromium.org src/net/quic/OWNERS The length in bytes of a QUIC REJ message received from the server. dschinazi@chromium.org src/net/quic/OWNERS The number of consecutive times a packet was retried after a write error, using exponential backoff. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error code which resulted in a stream being reset by the client. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error code which resulted in a stream being reset by the server. dschinazi@chromium.org src/net/quic/OWNERS The number of request for secure resources over QUIC sessions. True if the session is secure, false if it is not. dschinazi@chromium.org src/net/quic/OWNERS When a SHLO handshake message is received, whether the client IP address and port number in it differ from the local client IP address and port number. In the comparison, the first address is the one in SHLO and the second address is the client IP address. dschinazi@chromium.org src/net/quic/OWNERS The size in bytes of an encrypted QUIC packet sent to the peer at the specified encryption level. dschinazi@chromium.org src/net/quic/OWNERS The largest packet which the client received from the server during the session. dschinazi@chromium.org src/net/quic/OWNERS The final smoothed RTT observed during the life of a QUIC connection. renjietang@chromium.org src/net/quic/OWNERS True if fresh host lists contains stale host used in racing connection. renjietang@chromium.org src/net/quic/OWNERS The time a QUIC connection from invalid stale dns result takes to do Crypto handshake. This starts on DoConnect and ends when the connection finishes. renjietang@chromium.org src/net/quic/OWNERS Records when a STATELESS_RESET is received after a connectivity probing is cancelled. renjietang@chromium.org src/net/quic/OWNERS When probing is cancelled, records whether a STATELESS_RESET is received. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error code that we sent in a STOP_SENDING frame. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error code that we received in a STOP_SENDING frame. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error code which resulted in the stream (and connection) being closed by the client after the handshake was confirmed. dschinazi@chromium.org src/net/quic/OWNERS The QUIC error code which resulted in the stream (and connection) being closed by the client after the handshake was confirmed. dschinazi@chromium.org src/net/quic/OWNERS Whether any of QUIC session's streams are flow control blocked when a PING message is sent to server. dschinazi@chromium.org src/net/quic/OWNERS The number of stream frames received which were duplicates, out of every 1000 stream frames received. Only for QUIC sessions which received at least 100 packets. dschinazi@chromium.org src/net/quic/OWNERS The percentage of stream frames received which were duplicates. Only for QUIC sessions which received at least 100 packets. dschinazi@chromium.org src/net/quic/OWNERS The percentage of stream frames received which were duplicates. Only for QUIC sessions which received fewer than 100 packets. dschinazi@chromium.org src/net/quic/OWNERS The number of stream frames received which were duplicates, out of every 1000 stream frames received. Only for QUIC sessions which received fewer than 100 packets. dschinazi@chromium.org src/net/quic/OWNERS If a QUIC connection timed out with open streams, this contains a count of consecutive PTOs. dschinazi@chromium.org src/net/quic/OWNERS If a QUIC connection timed out with open streams, this contains a count of consecutive RTOs. dschinazi@chromium.org src/net/quic/OWNERS If a QUIC connection timed out with open streams, this contains a count of consecutive TLPs. dschinazi@chromium.org src/net/quic/OWNERS If a QUIC connection timed out with open streams, this will be true when the connection has unacked packets. dschinazi@chromium.org src/net/quic/OWNERS If a QUIC connection timed out locally with open streams, this contains the local port number for the connection. renjietang@chromium.org src/net/quic/OWNERS The time a QuicStreamFactory Job takes from host rersolution to connection confirmation. dschinazi@chromium.org src/net/quic/OWNERS True if more than 100 streams are open when a new stream is activated. dschinazi@chromium.org src/net/quic/OWNERS When a QUIC packet is sent at initial encryption that is smaller than the minimum size, this records the size difference (minimum_size - observed_size). dschinazi@chromium.org src/net/quic/OWNERS The number of undecryptable packets recevied by a QuicSession when the session is closed. Includes packets where a decryption key was not present. dschinazi@chromium.org src/net/quic/OWNERS The number of undecryptable packets recevied by a QuicSession when the session is closed. Only includes packets where a decryption key was present for the packet's encryption level. renjietang@chromium.org src/net/quic/OWNERS The time a QUIC connection that will be confirmed takes for Crypto handshake. The event starts on DoConnect, and ends when the connection finishes. dschinazi@chromium.org src/net/quic/OWNERS Time spent verifying the signature and certificate chain. This is logged whenever QUIC verifies the certificate chain and signature during crypto handshake. Warning: this histogram was expired from 09/12/2022 to 03/22/2023; data may be missing. dschinazi@chromium.org src/net/quic/OWNERS The network error code returned when attempting to write to a QUIC connection. dschinazi@chromium.org src/net/quic/OWNERS The network error code returned when attempting to write to a QUIC connection after the handshake has been confirmed. dschinazi@chromium.org src/net/quic/OWNERS The most recent network error code when attempting to write to a QUIC connection when the network gets disconnected. dschinazi@chromium.org src/net/quic/OWNERS The reason QUIC packet writer needed to allocate a new buffer, rather than the expected case of reusing its existing one. dschinazi@chromium.org src/net/quic/OWNERS Indicates whether a QUIC handshake attempted or used 0-RTT on the connection, and if 0-RTT was not used, it provides reasons why. renjietang@chromium.org src/net/quic/OWNERS Indicates whether a QUIC handshake attempted or used 0-RTT on the connection, and if 0-RTT was not used, it provides reasons why. Only records connections with Google hosted servers. renjietang@chromium.org src/net/quic/OWNERS Indicates whether a QUIC handshake attempted or used 0-RTT on the connection, and if 0-RTT was not used, it provides reasons why. Only records connections with non-Google servers. renjietang@chromium.org src/net/quic/OWNERS Whether 0-RTT was successfully used in the connection. dschinazi@chromium.org src/net/quic/OWNERS Records if a new connection on the alternate network is attempted when a connection fails before handshake is confirmed. dschinazi@chromium.org src/net/quic/OWNERS Connection type of the default network when the connection fails with handshake not confirmed. dschinazi@chromium.org src/net/quic/OWNERS A count of how often a user hits 1, 2, 3, 4 and 5 bad packet loss events for port 443. Recorded whenever QUIC has bad packet loss (high packet loss on multiple consecutive connections). dschinazi@chromium.org src/net/quic/OWNERS Status of the connection on the non-default network when it finishes. A connection may stay on the non-default network during the initial setup when the platform's default network changes. dschinazi@chromium.org src/net/quic/OWNERS Records, for initial socket created for each new QUIC connection, whether the bound network matched the default network tracked by QuicStreamFactory. dschinazi@chromium.org src/net/quic/OWNERS Rrecords reasons QUIC is disabled (for all ports), if sufficent recent connections experience: public reset post crypto handshake, or timeouts with streams open. QUIC is disabled until the next reboot of Chrome. Logged during session close. renjietang@chromium.org src/net/quic/OWNERS Log the location in QuicStreamFactory where QUIC_PROTOCOL_ERROR is reported. dschinazi@chromium.org src/net/quic/OWNERS Connection type of the alternate network when a connection is about to be attempted when the original connection fails on the default network with handshake not confirmed. dschinazi@chromium.org src/net/quic/OWNERS Status of the connection which is created for migration before handshake is confirmed. dschinazi@chromium.org src/net/quic/OWNERS The network error code returned when the retried connection on the alternate network before handshake fails. dschinazi@chromium.org src/net/quic/OWNERS Captures whether the default network has been changed when the new connection succeeds on the "alternate" network. dschinazi@chromium.org src/net/quic/OWNERS Captures the maximum number of public resets post handshake that occurred within a window of recent connections (default 20). Will help inform the choice of threshold to disable QUIC for clients that experience pathalogical errors. Logged during session close. dschinazi@chromium.org src/net/quic/OWNERS Recorded whenever QUIC is disabled for a port due to repeated lossy connections (high packet loss on multiple consecutive connections). QUIC is disabled until next reboot of Chrome. dschinazi@chromium.org src/net/quic/OWNERS Captures the maximum number of connection timeouts with streams open that occurred within a window of recent connections (default 20). Will help inform the choice of threshold to disable QUIC for clients that experience pathalogical errors. Logged during session close. csharrison@chromium.org rsleevi@chromium.org The total number of redirects encountered during processing a URLRequest. This includes redirects generated by servers (for example, 302 Found) and redirects generated internally (for example, HSTS redirects or error pages). eustas@chromium.org True for redirect responses with unadvertised "Content-Encoding". False for valid redirect responses. See http://crbug.com/714514 rodneyding@google.com src/net/reporting/OWNERS The type of header received for configuring reporting API endpoints, recorded when reporting API headers are successfully parsed. rodneyding@google.com src/net/reporting/OWNERS The type of header that produced the endpoint used for uploading reports for the Reporting API, recorded when reports have been succesfully uploaded, counted once for each report. clamy@chromium.org When starting a cross-site navigation, the time between reading the headers and body of the response. dylancutler@google.com src/net/cookies/OWNERS Logged whenever a partitioned cookie is set from a renderer process, which can be from either document.cookie or the CookieStore API. True if the partition key was set with the FromScript constructor (used by the CookieStore API) or if the partition key matches the RestrictedCookieManager's internal partition key (which is the case for cookies set/modified by document.cookie). carlscab@google.com olivierli@chromium.org woa-performance@google.com Counts the number of RestrictedCookieManager::GetCookiesString IPCs received over 30 second periods at the Network Service. We start recording the metric when the Network Service is created and keep updating it for the entire lifetime of the Network Service process. dylancutler@google.com src/net/cookies/OWNERS Logs the number of partitioned cookies accessed by a script. Logged only when partitioned cookies are enabled. dylancutler@google.com src/net/cookies/OWNERS True iff the cookie set by RestrictedCookieManager is a partitioned cookie. Only logged when partitioned cookies are enabled and the cookie set by RCM will be accepted. morlovich@chromium.org src/net/cookies/OWNERS Logged on any document.cookie or CookieStore API operation. True if the browser-side site_for_cookies and the render-provided value match. morlovich@chromium.org src/net/cookies/OWNERS Logged on any document.cookie or CookieStore API operation. True if the browser-side top_frame_origin and the render-provided value match. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The size of shared dictionary written on disk. Emitted when SharedDictionaryManagerOnDisk succeeded to store the dictionary in disk cache and database. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The number of dictionaries evicted as there is no matching disk cache entry. Emitted when MismatchingEntryDeletionTask finishes. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The number of disk cache entries evicted as the key is invalid for token. Emitted when MismatchingEntryDeletionTask finishes. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The number of disk cache entries evicted as there is no matching metadata. Emitted when MismatchingEntryDeletionTask finishes. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The total count of shared dictionary on disk. Emitted when SharedDictionaryManagerOnDisk succeeded to store a dictionary in disk cache and database. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The total size of shared dictionary on disk. Emitted when SharedDictionaryManagerOnDisk succeeded to store a dictionary in disk cache and database. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The time taken to open a disk cache entry of a shared dictionary. Recorded when the entry is opened in the SharedDictionaryOnDisk. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The time taken to read the data of a shared dictionary's disk cache entry. Recorded when the whole data is read in the SharedDictionaryOnDisk. horo@chromium.org src/net/extras/shared_dictionary/OWNERS Records whether the shared dictionary metadata has been read when GetDictionary() is called for the first time. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The time taken to read shared dictionary metadata from the database. Recorded when SharedDictionaryStorageOnDisk receives the result. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The count of shared dictionary per top frame site on metadata. Emitted when SQLitePersistentSharedDictionaryStore is writing a dictionary in the database. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The size of shared dictionary per top frame site on metadata. Emitted when SQLitePersistentSharedDictionaryStore is writing a dictionary in the database. horo@chromium.org src/net/extras/shared_dictionary/OWNERS Records the status (OK or error code) returned by SQLitePersistentSharedDictionaryStore. Recorded when the database operation finishes. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The delay of SharedDictionaryTransaction caused by reading a shared dictionary. Recorded when the dictionary is read in the SharedDictionaryTransaction. horo@chromium.org src/net/extras/shared_dictionary/OWNERS The size of shared dictionary written in memory. Emitted when SharedDictionaryWriterInMemory succeeded to store the dictionary in memory. dschinazi@chromium.org src/net/OWNERS The size of a socket's receive buffer when the attempt to change it via setsockopt failed. dschinazi@chromium.org src/net/OWNERS The size of a socket's send buffer when the attempt to change it via setsockopt failed. dschinazi@chromium.org src/net/OWNERS The counts of the flow control state of each frame (with stream and session flow control on). dschinazi@chromium.org src/net/OWNERS The percent compression achieved when compressing HEADERS frames. dschinazi@chromium.org src/net/OWNERS Status of checking if a SPDY domain can handle a IP match. If a match is found, we successfully used the IP Pooling. If a match is not found, we could have used IP Pooling, except the TLS Cert didn't match the IP-pooled domain. Removed 2023-05. dschinazi@chromium.org src/net/OWNERS This histogram is recorded exactly once for every PUSH_PROMISE frame received on an HTTP/2 connection, and tracks the fate of the pushed stream. dschinazi@chromium.org src/net/OWNERS HTTP status codes received in HTTP/2 HEADERS frames. If a stream contains one or more informational (1xx) response preceeding the main response, each status code is logged separately. bnc@chromium.org src/net/OWNERS Records whether the HTTP/2 session received an Accept-CH entry for the given origin, which GetAcceptChViaAlps() returns. Logged every time SpdyHttpStream::GetAcceptChViaAlps() is called, typically once for each request that is served over HTTP/2. bnc@chromium.org src/net/OWNERS Records both whether there are any valid origin fields and whether there are any invalid ones in ACCEPT_CH frames. Logged once for each TLS handshake of a HTTP/2 connection if ALPS is negotiated, regardless of the number of ACCEPT_CH frames received in ALPS. bnc@chromium.org src/net/OWNERS Records the status (OK or error code) returned by AlpsDecoder when parsing ALPS data. Logged once for each TLS handshake of a HTTP/2 connection if ALPS is negotiated. arichiv@chromium.org src/net/OWNERS Net.SpdySession.AlpsDecoderStatus records errors returned by the AlpsDecoder class in HTTP/2 responses. Errors logged to that histogram cause a session termination, which isn't always desired. This histogram records errors that we want to note, but that shouldn't stop the connection. bnc@chromium.org src/net/OWNERS Records the total number of setting parameters received in SETTINGS frames in ALPS. Logged once for each TLS handshake of a HTTP/2 connection if ALPS is negotiated, regardless of the number of SETTINGS frames received in ALPS. dschinazi@chromium.org src/net/OWNERS Net error codes when SpdySession was closed. dschinazi@chromium.org src/net/OWNERS Socket connected status in SpdySession::CreateStream. bnc@chromium.org src/net/OWNERS Records the error code value received in each HTTP/2 GOAWAY frame. Removed 2023-06. dschinazi@chromium.org src/net/OWNERS The number of bytes that is pushed but not used when the session is closed. Removed 2023-06. dschinazi@chromium.org src/net/OWNERS The number of bytes that is pushed when the session is closed. bashi@chromium.org src/net/OWNERS Records the error code value received in each HTTP/2 RST_STREAM frame. dschinazi@chromium.org src/net/OWNERS Whether the server has advertised support for WebSockets over HTTP/2. dschinazi@chromium.org src/net/OWNERS The type of SPDY Protocol error encountered. dschinazi@chromium.org src/net/OWNERS WARNING: r181910 added an enum value in the middle, so don't trust the counts for values 9 and above for Chrome builds after that revision. The type of SPDY Protocol error encountered when talking to a google.com server. dschinazi@chromium.org src/net/OWNERS The type of SPDY Session used when looking up a session. dschinazi@chromium.org src/net/OWNERS Whether SpdySession::Get{Peer,Local}Address was called when the connection had no socket. dschinazi@chromium.org src/net/OWNERS The number of pushed, but abandoned streams over a single session. dschinazi@chromium.org src/net/OWNERS The number of streams issued over a single session. Removed 2023-06. dschinazi@chromium.org src/net/OWNERS The number of pushed, and used streams over a single session. Removed 2023-06. dschinazi@chromium.org src/net/OWNERS The number of push streams received over a single session. davidben@chromium.org trusty-transport@chromium.org For each TLS connection that offered Encrypted ClientHello (ECH), what was the result of that connection. In particular, this measures if the recovery flow was needed and, if so, whether it fixed the connection. agl@chromium.org rsleevi@chromium.org The SSL/TLS cipher suite that was negotiated. Recorded for each SSL/TLS connection in the socket pool where Connect() succeeds. agl@chromium.org Counts of specific error codes returned when opening an SSL connection. davidben@chromium.org trusty-transport@chromium.org Counts of specific error codes returned when opening an SSL connection. Recorded for connections to servers that advertise support for Encrypted ClientHello (ECH) in DNS. (Specifically, connections where the HTTPS record used included an ECHConfigList.) agl@chromium.org Time from when the Connect() starts until it completes. davidben@chromium.org trusty-transport@chromium.org Time from when the Connect() starts until it completes. Recorded for successful connections to servers that advertise support for Encrypted ClientHello (ECH) in DNS. (Specifically, connects where the HTTPS record used included an ECHConfigList.) agl@chromium.org rsleevi@chromium.org sigbjorn@opera.com The curve used for key exchange for ECDHE. Recorded for each SSL/TLS connection in the socket pool where Connect() succeeds. rsleevi@chromium.org Time to complete a certificate verification (success case). rsleevi@chromium.org Time to complete a certificate verification (error case). davidben@chromium.org src/net/OWNERS For each non-resumption TLS handshake that sends a client certificate, the signature algorithm used by the client. davidben@chromium.org src/net/OWNERS For each successful TLS handshake, what kind of handshake was used. This metric distinguishes TLS 1.2 (or earlier) and TLS 1.3 as they have very different resumption and round-trip behaviors. It also distinguishes full handshakes, resumption, 0-RTT, and False Start. davidben@chromium.org svaldez@chromium.org src/net/OWNERS Indicates whether a TLS 1.3 connection ended up using 0-RTT or not, and why; this includes reasons such as the server declining to resume the connection and the client not having enough tickets available. This metric is only recorded if 0-RTT supported is enabled in the client. davidben@chromium.org trusty-transport@chromium.org Indicates whether a TLS 1.3 connection to a Google host ended up using 0-RTT or not, and why; this includes reasons such as the server declining to resume the connection and the client not having enough tickets available. This metric is only recorded if 0-RTT supported is enabled in the client. cthomp@chromium.org trusty-transport@chromium.org Counts when the SSLKEYLOGFILE environment variable or --ssl-key-log-file command-line flag are set, and when they enable the SSLKeyLogger feature. This histogram was temporarily expired from M92 until M104. Replaced by Net.SSLLegacyCryptoFallback2. This one incorrectly counted all SHA-1-based algorithms in certificates, rather than just RSASSA-PKCS1-v1_5. davidben@chromium.org trusty-transport@chromium.org For each TLS connection, whether it needed the legacy crypto fallback and a classification as to why. See https://crbug.com/658905 and https://crbug.com/691888. Note some connections are reported as sending SHA-1 certificates because, although SHA-1 is no longer accepted in certificates, servers may send unused certificates in the handshake. Some such servers additionally match their certificate chains against the ClientHello. These servers require the client advertise legacy algorithms despite not actually using them. davidben@chromium.org trusty-transport@chromium.org For each TLS connection, whether it needed the legacy crypto fallback and a classification as to why. See https://crbug.com/658905 and https://crbug.com/691888. Note some connections are reported as sending SHA-1 certificates because, although SHA-1 is no longer accepted in certificates, servers may send unused certificates in the handshake. Some such servers additionally match their certificate chains against the ClientHello. These servers require the client advertise legacy algorithms despite not actually using them. dschinazi@chromium.org src/net/OWNERS For each TLS handshake, whether ALPN was negotiated; and if so, the negotiated protocol. davidben@chromium.org src/net/OWNERS For each TLS handshake, whether the server supports the renegotiation_info extension (RFC 5746). If the server negotiated TLS 1.3, which removed renegotiation, it is considered to support the extension. Servers that do not support it are potentially vulnerable to an attack involving TLS renegotiation. davidben@chromium.org For each TLS connection which uses a unknown root, an RSA key, and TLS 1.2 or below, what the result of checking the RSA key usage would have been. davidben@chromium.org src/net/OWNERS For each SSL connection with a full handshake using a DHE- or ECDHE-based key exchange, the signature algorithm used to authenticate the peer. In TLS 1.2, this is the signature on the ServerKeyExchange message. (Note: Although the ECDSA values specify a curve, the curve is only enforced in TLS 1.3.) davidben@chromium.org The SSL/TLS version that was negotiated. Recorded for each SSL/TLS connection in the socket pool where Connect() succeeds. davidben@chromium.org rsleevi@chromium.org The SSL/TLS version that was negotiated to a Google host. Recorded for each appplicable SSL/TLS connection in the socket pool where Connect() succeeds. Google servers all support TLS 1.2, so any occurrences of TLS 1.0 or TLS 1.1 indicate an outdated insecure TLS MITM proxy, such as some antivirus configurations. TLS 1.0 and 1.1 are deprecated, so record these to see how prevalent they are. See https://crbug.com/896013. mmenke@chromium.org Time from when the Connect() starts until it completes. Only times under 10 minutes are logged. Removed 2022-02. mgersh@chromium.org Time from when the Connect() starts until it completes when the network address only contains IPv4 addresses. Only times under 10 minutes are logged. Removed 2022-02. mgersh@chromium.org Time from when the Connect() starts until it completes when the IPv4 fallback connection won the race against IPv6. Only times under 10 minutes are logged. Removed 2022-02. mgersh@chromium.org Time from when the Connect() starts until it completes when we race an IPv6 connection against an IPv4 connection with a 300ms delay. Only times under 10 minutes are logged. Removed 2022-02. mgersh@chromium.org Time from when the Connect() starts until it completes when the network address only contains IPv6 addresses. Only times under 10 minutes are logged. bashi@chromium.org src/net/OWNERS Time taken when failed to establish a TCP connection to an individual endpoint. This includes the case when the attempt was aborted by a higher layer (likely because it took too long). bashi@chromium.org src/net/OWNERS Time taken to successfully establish a TCP connection to an individual endpoint. bmcquade@chromium.org The kernel's estimated TCP round trip time. Recorded for each TCP socket, at the time it is disconnected. svaldez@chromium.org timhuber@google.com yhirano@chromium.org The net error for a failed Fetch API call with an associated Trust Tokens operation. This was originally added to help debug a surfeit of 'TypeError: failed to fetch' observed in live testing, and it is now retained since it's useful for ongoing health monitoring. svaldez@chromium.org timhuber@google.com The //net status codes for resource requests that had started Trust Tokens operations. This captures the reasons why requests with Trust Tokens operations fail and might help debug a surfeit of "TypeError: failed to fetch" observed in live testing. svaldez@chromium.org timhuber@google.com Time taken to execute various parts of a Trust Tokens operation: 1. Begin = time taken to execute the operation's outbound Begin half 2. Server = time from the end of the outbound Begin half to the beginning of the inbound Finalize half 3. Finalize = time taken to execute the inbound Finalize half 4. Total = Begin + Server + Finalize (only recorded for operations that see server responses) The other variants (see histogram_suffixes_list's TrustTokenOperationType entry): 1. Outcome (Success or Failure) 2. The type of Trust Tokens operation 3. Whether the operation was platform-provided (i.e. executed by a method other than a direct HTTP request to the issuer's server) svaldez@chromium.org timhuber@google.com Whether the Trust Tokens redemption logic received an empty redemption request string from its underlying cryptographic library. If this is always true, but servers occasionally see empty redemption request headers, it might suggest middleware (namely extensions) is removing the headers' values. svaldez@chromium.org timhuber@google.com For resource requests that bear Trust Tokens parameters, the results of running TrustTokenRequestHelperFactory to initialize Trust Tokens handling logic. This might help debug a surfeit of failed Trust Tokens issuance operations observed in live testing. mgersh@chromium.org Chromium error code from call to RandomBind() UDP socket. dschinazi@chromium.org src/net/OWNERS The time spent in closesocket call in UDPSocketWin::Close. cduvall@chromium.org jam@chromium.org Measures time {Throttle} deferred a request on WillProcessResponse. Logged every time {Throttle} defers a request. cduvall@chromium.org jam@chromium.org Measures time {Throttle} deferred a request on WillStartRequest. Logged every time {Throttle} defers a request. cduvall@chromium.org jam@chromium.org Measures time a URLLoaderThrottle was deferred when on {Stage}. Logged every time a throttle defers a request. cduvall@chromium.org jam@chromium.org Measures time a URLLoaderThrottle took to execute {Stage}. Logged every time a throttle runs. davidvc@chromium.org kaustubhag@chromium.org Records for each URLRequest whether its referrer contains more information than just its origin (this is the case exactly when it has at least one character apart from a leading slash in its path, e.g. http://example.com/a but not http://example.com/ nor http://example.com). davidvc@chromium.org kaustubhag@chromium.org Records the distribution of referrer policies provided with outgoing URLRequests, and whether or not the requests were cross-origin. ricea@chromium.org blink-network-stack@google.com Positive net error codes that WebSockets end with, including OK and ABORTED. bashi@chromium.org blink-network-stack@google.com Fallback result of WebSocket handshakes. Recorded when a WebSocket handshake completed. yhirano@chromium.org ricea@chromium.org src/net/OWNERS Results of WebSocket handshakes, including information whether the handshake happened over HTTP/1, HTTP/2 or HTTP/3. Use this histogram as a baseline for investigating feature usage counters. yhirano@chromium.org ricea@chromium.org All HTTP status codes seen during WebSocket handshakes. bashi@chromium.org blink-network-stack@google.com Negotiated HTTP Datagram version. Recorded when a WebTransport session becomes ready. bashi@chromium.org blink-network-stack@google.com Negotiated WebTransport version. Recorded when a WebTransport session becomes ready. nidhijaju@chromium.org blink-network-stack@google.com Compressed/Decompressed size ratio as a percentage when using zstd. nidhijaju@chromium.org blink-network-stack@google.com Error code observed after failing to decode a Zstd-compressed response stream from the network. Recorded once per layer of Zstd compression that encountered a decoding error. See Net.ZstdFilter.Status to get the overall error rate. nidhijaju@chromium.org blink-network-stack@google.com The maximum memory allocation by the zstd library to decode a Zstd-compressed response stream from the network. Recorded once per layer of Zstd compression (usually once per zstd-compressed response), at the end of decoding. nidhijaju@chromium.org blink-network-stack@google.com The final state of the ZstdFilter. Recorded once per layer of Zstd compression (usually once per zstd-compressed response), at the end of decoding.