File: metrics_features.h

package info (click to toggle)
chromium 120.0.6099.224-1~deb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 6,112,112 kB
  • sloc: cpp: 32,907,025; ansic: 8,148,123; javascript: 3,679,536; python: 2,031,248; asm: 959,718; java: 804,675; xml: 617,256; sh: 111,417; objc: 100,835; perl: 88,443; cs: 53,032; makefile: 29,579; fortran: 24,137; php: 21,162; tcl: 21,147; sql: 20,809; ruby: 17,735; pascal: 12,864; yacc: 8,045; lisp: 3,388; lex: 1,323; ada: 727; awk: 329; jsp: 267; csh: 117; exp: 43; sed: 37
file content (61 lines) | stat: -rw-r--r-- 2,753 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
// Copyright 2022 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#ifndef COMPONENTS_METRICS_METRICS_FEATURES_H_
#define COMPONENTS_METRICS_METRICS_FEATURES_H_

#include "base/feature_list.h"
#include "base/metrics/field_trial_params.h"

namespace metrics::features {

// Determines at what point the metrics service is allowed to close a log when
// Chrome is closed (and backgrounded/foregrounded for mobile platforms). When
// this feature is disabled, the metrics service can only close a log if it has
// already started sending logs. When this feature is enabled, the metrics
// service can close a log starting from when the first log is opened.
BASE_DECLARE_FEATURE(kMetricsServiceAllowEarlyLogClose);

// This can be used to disable structured metrics as a whole.
BASE_DECLARE_FEATURE(kStructuredMetrics);

#if BUILDFLAG(IS_ANDROID)
// Determines whether to merge histograms from child processes when Chrome is
// backgrounded/foregrounded. Only on Android.
BASE_DECLARE_FEATURE(kMergeSubprocessMetricsOnBgAndFg);
#endif  // BUILDFLAG(IS_ANDROID)

// Determines whether to allow merging subprocess metrics asynchronously. By
// itself, the feature does nothing. But the different params below allow
// toggling specific async behaviours.
BASE_DECLARE_FEATURE(kSubprocessMetricsAsync);
// Determines whether to merge subprocess metrics asynchronously when creating
// periodic ongoing UMA logs.
extern const base::FeatureParam<bool> kPeriodicMergeAsync;
// Determines whether to merge the last metrics of a subprocess that has just
// exited asynchronously.
extern const base::FeatureParam<bool> kDeregisterAsync;
// Determines whether the tasks posted when deregistering a subprocess
// asynchronously are sequenced. This param only applies when |kDeregisterAsync|
// is true.
extern const base::FeatureParam<bool> kDeregisterSequenced;

// Determines whether to schedule a flush of persistent histogram memory
// immediately after writing a system profile to it.
BASE_DECLARE_FEATURE(kFlushPersistentSystemProfileOnWrite);

// Determines whether to perform histogram delta snapshots in a background
// thread (in contrast to snapshotting unlogged samples in the background, then
// marking them as logged on the main thread).
BASE_DECLARE_FEATURE(kMetricsServiceDeltaSnapshotInBg);

// Determines whether to always flush Local State immediately after an UMA/UKM
// log upload. If this is disabled, Local State is only immediately flushed
// after an upload if this is a mobile platform and the browser is in the
// background.
BASE_DECLARE_FEATURE(kReportingServiceAlwaysFlush);

}  // namespace metrics::features

#endif  // COMPONENTS_METRICS_METRICS_FEATURES_H_