Description

In T353680#9424126, @Dbrant wrote:

• The problem seems to be that the Metrics client library sends the event to both streams at once, but doesn't use the correct schema name when sending them. Rather, it uses the schema name from product_metrics for both streams, so the metrics_platform event is getting rejected because it's part of a different schema.

As I understand this bug report, what's happening is multiple streams that use divergent schemas are defined as listening to the same event. Currently, the Java MPC broadcasts events – it will submit an event to any stream that has declared interest in it – whereas the JS and PHP MPCs don't.

To fix this we could:

1. Remove the android.metrics_platform.* stream definitions
2. Patch the Java MPC to not broadcast events and deploy a new version of the Android app that uses it

AIUI 1 is preferable but might be blocked because we still want to collect data on the android.metrics_platform.* streams.

Acceptance Criteria

Required

• Unit/Integration tests
• Documentation
• Passed QA?