File: ukm_reporting_ios_util.h

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (26 lines) | stat: -rw-r--r-- 1,275 bytes parent folder | download | duplicates (11)
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
// Copyright 2020 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_UKM_IOS_UKM_REPORTING_IOS_UTIL_H_
#define COMPONENTS_UKM_IOS_UKM_REPORTING_IOS_UTIL_H_

// Utilities in this file should help to figure out the root cause of
// crbug.com/1154678 (Data loss on UMA in iOS). If total sum of
// "UKM.IOSLog.OnSuccess" is greater than total count of "UKM.LogSize.OnSuccess"
// records, then data loss is caused by failure to write the histogram to the
// disk on background thread. Otherwise (if total sum of
// "UKM.IOSLog.OnSuccess" is equal to total count of "UKM.LogSize.OnSuccess"
// records) then there is actually no data loss and app simply gets terminated
// in a short window between UKM reached the server and the API call which
// records the data.

// Records "UKM.IOSLog.OnSuccess" histogram and resets the counter.
void RecordAndResetUkmLogSizeOnSuccessCounter();

// Increments the counter which will be recorded as UMA histogram when
// RecordAndResetUkmLogSizeOnSuccessCounter is called. Counter represents
// number of times "UKM.LogSize.OnSuccess" was recorded.
void IncrementUkmLogSizeOnSuccessCounter();

#endif  // COMPONENTS_UKM_IOS_UKM_REPORTING_IOS_UTIL_H_