eventlogging-valid-mixed was originally created to contain (almost) all eventlogging topics in one topic for backwards compatibility with old Zero-MQ based clients. We then also used it for the eventlogging-consumer MySQL to ingest an includelist of event topics into the eventlogging MySQL database, which was deprecated and removed in T159170: Sunset MySQL data store for eventlogging.
I don't think there are any active consumers of eventlogging-valid-mixed, so we should stop producing to it.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Remove eventlogging-valid-mixed output for eventlogging-processor | operations/puppet | production | +1 -181 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ottomata | T185233 Modern Event Platform | |||
| Open | Ottomata | T238230 Decommission EventLogging backend components by migrating to MEP | |||
| Resolved | Ottomata | T265651 Disable eventlogging-valid-mixed topic |
Change 634317 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/puppet@production] Remove eventlogging-valid-mixed output for eventlogging-processor
Change 634317 merged by Ottomata:
[operations/puppet@production] Remove eventlogging-valid-mixed output for eventlogging-processor
Mentioned in SAL (#wikimedia-analytics) [2020-10-20T15:00:50Z] <ottomata> disabling sending EventLogging events to eventlogging-valid-mixed topic - T265651