• Home
Name Date Size #Lines LOC

..--

READMED07-May-20241.5 KiB3825

chrome_user_metrics_extension.protoD07-May-20242.9 KiB7362

histogram_event.protoD07-May-20242.2 KiB6051

system_profile.protoD07-May-202429 KiB760640

user_action_event.protoD07-May-20241.1 KiB3630

README

1Copyright (C) 2015 The Android Open Source Project
2
3Licensed under the Apache License, Version 2.0 (the "License");
4you may not use this file except in compliance with the License.
5You may obtain a copy of the License at
6
7     http://www.apache.org/licenses/LICENSE-2.0
8
9Unless required by applicable law or agreed to in writing, software
10distributed under the License is distributed on an "AS IS" BASIS,
11WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12See the License for the specific language governing permissions and
13limitations under the License.
14
15
16
17
18This directory contains the protocol buffers used by the standalone metrics
19uploader. Those protobuffers are copied from the chromium protobuffers from
20https://chromium.googlesource.com/chromium/src/+/master/components/metrics/proto/
21at 3bfe5f2b4c03d2cac718d137ed14cd2c6354bfed.
22
23Any change to this protobuf must first be made to the backend's protobuf and be
24compatible with the chromium protobuffers.
25
26
27Q: Why fork the chromium protobuffers ?
28A: The standalone metrics uploader needs chromium os fields that are not defined
29by the chromium protobufs. Instead of pushing chromium os specific changes to
30chromium, we can add them only to chromium os (and to the backend of course).
31
32
33Q: What's the difference between those protobuffers and chromium's protobuffers?
34A: When the protobuffers were copied, some chromium specific protobuffers were
35not imported:
36* omnibox related protobuffers.
37* performance profiling protobuffers (not used in chromium os).
38