Stream Lineage and .NET consumers with default client id

Confluent’s .NET examples omit setting consumer client id, so it defaults to “rdkafka”.

Confluent’s Stream Lineage generates incorrect topologies when multiple consumer groups share the same client id. Stream Lineage includes a warning about this, which is helpful, but it would help further if

A) rdkafka lib defaulted to using “consumer-${consumerGroup}-${num}” like how Spring Kafka apps do OR
B) Confluent’s .NET examples included setting consumer client id OR
C) Stream Lineage were smart enough to recognize that two apps with same client id and different consumer groups are not the same app

Thanks for taking the time to comment @Ben. I’ll create a ticket to get the .NET getting started guides to set a unique consumer client id.

1 Like