I think this is a great update for the proposal. It’s clear that a lot of effort was put into answering previous complaints in a very comprehensive way.
I have doubts about one part:
Packages wanting to collect metrics data will need to depend on eos-metrics. For example, to collect statistics about Settings usage, the gnome-control-center package would need to depend on eos-metrics in order to send a metric to eos-event-recorder-daemon.
In general, the “client” will need to gracefully handle the state where the eos-metrics endpoint is not running. For example, the user may disable it, or it may crash, and other applications should still start and work without interruptions. Even if eos-metrics package is installed, there is no guarantee that the endpoint is running. So I don’t think the dependencies on eos-metric package are needed.
I think it’d be preferable to pull in eos-metrics package via comps, and let the stats collection happen if the endpoint is available, without any hard requirements.