• Home
Name Date Size #Lines LOC

..--

gpu/03-May-2024-230157

net/03-May-2024-663463

profiler/03-May-2024-843546

proto/03-May-2024-1,7401,403

serialization/03-May-2024-755526

BUILD.gnD03-May-20242.8 KiB125113

DEPSD03-May-202482 65

OWNERSD03-May-2024117 65

READMED03-May-20241 KiB2419

clean_exit_beacon.ccD03-May-20242.4 KiB8163

clean_exit_beacon.hD03-May-20241.3 KiB4622

client_info.ccD03-May-2024365 145

client_info.hD03-May-2024956 3918

cloned_install_detector.ccD03-May-20243 KiB9969

cloned_install_detector.hD03-May-20241.9 KiB6030

compression_utils.ccD03-May-20245.2 KiB157110

compression_utils.hD03-May-2024673 218

compression_utils_unittest.ccD03-May-20242.5 KiB7747

daily_event.ccD03-May-20242.9 KiB10781

daily_event.hD03-May-20243 KiB9337

daily_event_unittest.ccD03-May-20242.7 KiB9766

machine_id_provider.hD03-May-20241.7 KiB4718

machine_id_provider_stub.ccD03-May-2024514 2513

machine_id_provider_win.ccD03-May-20243.7 KiB11880

machine_id_provider_win_unittest.ccD03-May-2024628 2413

metrics_hashes.ccD03-May-20241 KiB4023

metrics_hashes.hD03-May-2024546 218

metrics_hashes_unittest.ccD03-May-2024925 3221

metrics_log.ccD03-May-202416.3 KiB438317

metrics_log.hD03-May-20247.2 KiB20289

metrics_log_manager.ccD03-May-20244.3 KiB13795

metrics_log_manager.hD03-May-20243.8 KiB11650

metrics_log_manager_unittest.ccD03-May-202411.1 KiB305224

metrics_log_unittest.ccD03-May-202414 KiB386292

metrics_log_uploader.ccD03-May-2024589 2213

metrics_log_uploader.hD03-May-20241.5 KiB4624

metrics_pref_names.ccD03-May-20245.9 KiB13855

metrics_pref_names.hD03-May-20241.8 KiB4636

metrics_provider.ccD03-May-2024904 4427

metrics_provider.hD03-May-20242.1 KiB6327

metrics_reporting_scheduler.ccD03-May-20245 KiB165114

metrics_reporting_scheduler.hD03-May-20242.6 KiB8333

metrics_reporting_scheduler_unittest.ccD03-May-20241.7 KiB6343

metrics_service.ccD03-May-202445.8 KiB1,224732

metrics_service.hD03-May-202417.8 KiB473193

metrics_service_client.ccD03-May-2024359 146

metrics_service_client.hD03-May-20242.7 KiB7330

metrics_service_unittest.ccD03-May-202413.6 KiB367256

metrics_state_manager.ccD03-May-202412 KiB316216

metrics_state_manager.hD03-May-20246.5 KiB16669

metrics_state_manager_unittest.ccD03-May-202414 KiB382247

metrics_switches.ccD03-May-2024488 166

metrics_switches.hD03-May-2024548 198

persisted_logs.ccD03-May-20245.5 KiB176130

persisted_logs.hD03-May-20244.9 KiB14265

persisted_logs_unittest.ccD03-May-20249.6 KiB287205

test_metrics_service_client.ccD03-May-20241.7 KiB6947

test_metrics_service_client.hD03-May-20241.8 KiB5334

README

1This component contains the base classes for the metrics service and only
2depends on //base. It is used by ChromeOS as the base for a standalone service
3that will upload the metrics when ChromeOS is not installed (headless install).
4
5This is the first step towards the componentization of metrics that will happen
6later this spring.
7
8A proposed structure for the metrics component is:
9//components/metrics/base,
10  Depends on base only. Contains the protobuf definitions.
11//components/metrics/core
12  Depends on everything iOS depends on
13//components/metrics/content
14  Depends on content
15
16Ideally, the component would abstract the network stack and have a clean
17separation between the metrics upload logic (protbuf generation, retry, etc...),
18the chrome part (gathering histogram from all the threads, populating the
19log with hardware characteristics, plugin state, etc.).
20
21It is a plus if the code currently in the component (i.e., the code that can
22depend only on //base) stays in a single directory as it would be easier
23for ChromeOS to pull it :).
24