Google Git
Sign in
chromium / chromium / src / components / reporting / refs/heads/main
commit5e1f7de57cd51642e8d01fe2aaa574857a73f076[log] [tgz]
authorJan Zarzycki <janzarzycki@google.com>Fri Dec 12 07:43:39 2025
committerCopybara-Service <copybara-worker@google.com>Fri Dec 12 07:51:45 2025
tree5c1215c38df1c27e2faed2034817aa5464a31bae
parentc80cc3c6f8d4fd0247d5cc00ac6bb0e97e3f11f1 [diff]
Add proto for SaaS domain usage reporting. Introduces SaaSDomainReportEvent to capture aggregated metrics about SaaS domain usage, including profile details and per-domain metrics like visit counts, content transfers, and encryption protocols. Adds SAAS_DOMAIN to Destination enum in record_constants.proto to support this new report type. Bug: 466008386 Change-Id: I09bb93b220f683b670f9427455c4139354203507 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7252549 Commit-Queue: Jan Zarzycki <janzarzycki@google.com> Reviewed-by: Dominique Fauteux-Chapleau <domfc@chromium.org> Reviewed-by: Igor Ruvinov <igorruvinov@chromium.org> Cr-Commit-Position: refs/heads/main@{#1557885} NOKEYCHECK=True GitOrigin-RevId: 28b433409da09f78cc35711a208e2e354d56c81a
1 file changed
tree: 5c1215c38df1c27e2faed2034817aa5464a31bae
  1. client/
  2. compression/
  3. encryption/
  4. health/
  5. metrics/
  6. proto/
  7. resources/
  8. storage/
  9. util/
  10. DIR_METADATA
  11. OWNERS
  12. PRESUBMIT.py
  13. README.md
README.md

The Encrypted Reporting Pipeline (ERP) provides a universal method for upload of data for enterprise customers.

The code structure looks like this:

Chrome:

  • //components/reporting
    Code shared between Chrome and ChromeOS.
  • //chrome/browser/policy/messaging_layer
    Code that lives only in the browser, primary interfaces for reporting data such as ReportQueueImpl and ReportQueueConfiguration.

ChromeOS:

  • //platform2/missived
    Daemon for encryption and storage of reports.

If you'd like to begin using ERP within Chrome please check the comment in //components/reporting/client/report_queue_provider.h.

Run Unit Tests

To run the unit tests for this directory, after having configured Chromium's build environment:

  1. Run autoninja -C out/Default components_unittests to build the components unit test executable.

  2. Then, run out/Default/components_unittests --gtest_filter='<target tests>' to run relevant tests. Here, <target tests> is a wildcard pattern (refer to the document of gtest for more details). For example, to run all tests for StorageQueue, run

    $ out/Default/components_unittests --gtest_filter='*/StorageQueueTest.*'

    For another example, to run all tests in this directory, run

    $ tools/autotest.py -C out/Default --run_all components/reporting

    You can also append a filter such as --gtest_filter='*/StorageQueueTest.*' to the line above.

    Another useful flag for dealing with flaky tests is --gtest_repeat=, which repeats tests for multiple times.

    For more gtest features, check out the gtest document.