Skip to content

Conversation

@cjreynol
Copy link
Collaborator

@cjreynol cjreynol commented Nov 18, 2025

Introduce a new binary to handle responsibility of transmitting metrics to Google. This is an intermediate step to moving the binary to a new cuttlefish-metrics package and having installation of that package be the enabler for metrics.

@cjreynol cjreynol self-assigned this Nov 18, 2025
@cjreynol cjreynol force-pushed the cuttlefish_metrics branch 4 times, most recently from 87fb9d0 to 71fb387 Compare November 24, 2025 23:08
@cjreynol cjreynol force-pushed the cuttlefish_metrics branch 2 times, most recently from a406fa3 to e5c7de7 Compare December 10, 2025 01:34
@cjreynol cjreynol added kokoro:force-run Trigger a presubmit build unconditionally. kokoro:run Run e2e tests. labels Dec 10, 2025
@GoogleCuttlefishTesterBot GoogleCuttlefishTesterBot removed kokoro:run Run e2e tests. kokoro:force-run Trigger a presubmit build unconditionally. labels Dec 10, 2025
@cjreynol cjreynol force-pushed the cuttlefish_metrics branch 5 times, most recently from da8fac3 to 882aec7 Compare December 11, 2025 23:14
@cjreynol cjreynol changed the title Introduce cuttlefish-metrics package Introduce metrics-transmitter binary Dec 11, 2025
The idea is to move all of the Google-specific logic into this new
binary, then make the binary part of a new package that enables metrics
transmission when the package is installed.  The package will be
introduced later.

This commit introduces the binary with duplicate code from the existing
conversion and transmission logic, but does not use
it or remove the copied code.

Bug: 450053679
The team-owned `CuttlefishLogEvent` proto is the new external boundary
for the `cvd`-based metrics code.  The Google-specific protos and
information now all lives in the new `metrics-transmitter` binary, which
allows it to be replaced with something not specific to Google.

Bug: 450053679
I want to reference both the enum values and strings in multiple places,
so I am isolating it to avoid unnecessary dependency chains.
Re-introducing the capability for transmitting metrics, if the boolean
enabled flag is set, after the transmission call was removed in a
previous commit when adjusting the API boundaries.

Bug: 450053679
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants