Summary: Move ukm components to a metrics mojo service (was: Move ukm components to a metrics service)
Please note that "metrics service" is already a thing (components/metrics/metrics_service.cc) so using that term to refer to the mojo service is confusing, because you're referring to something else than metrics_service.cc.
I guess I misunderstood since I don't know much about serviceication - i thought having it be a mojo interface would be enough for other processes to be able to collect to UKM.
Would you mind giving a bit more information here on what this would allow us to do, or is this an improvement needed for all mojo interfaces?
My understanding is that, right now UKM's mojo interface is a capability off the browser process, rather than as a capability of a UKM service.
Moving forward, rather than UKM running as a service, it may make sense to just have it be a capability of a larger metrics service.
Either way, the next step is probably to convert it to being a capability off of an metrics/ukm service embedded in the browser process. I don't know that that makes it more broadly usable currently, but it would mean less change if metrics stopped being embedded in the browser and could run independently.
Comment 1 by asvitk...@chromium.org
, Jun 16 2017