Change Details

The eventlogging client python module installed on tin.eqiad.wmnet doesn't support Kafka. Which more and more stuff moving away from ZMQ, this makes it impossible to test or debug event streams. Not unless there is another host I can access that does have a working eventlogging-kafka client. It should probably also be installed on terbium instead of tin to discourage running of such processes on the deployment host.

The eventlogging client python module installed on tin.eqiad.wmnet doesn't support Kafka. Which more and more stuff moving away from ZMQ, this makes it impossible to test or debug event streams. Not unless there is another host I can access that does have a working eventlogging-kafka client. It should probably also be installed on terbium instead of tin to discourage running of such processes on the deployment host. ---- * {T87036}

The eventlogging client python module installed on tin.eqiad.wmnet doesn't support Kafka. Which more and more stuff moving away from ZMQ, this makes it impossible to test or debug event streams. Not unless there is another host I can access that does have a working eventlogging-kafka client. It should probably also be installed on terbium instead of tin to discourage running of such processes on the deployment host. ---- * {T87036}