Be able to define a customer group id for Kafka inputs.
Current Behavior
There is a hardcoded customer group id set to graylog2.
public class KafkaTransport extends ThrottleableTransport {
public static final String GROUP_ID = "graylog2";
...
Possible Solution
Allow user to supply the name through UI for each Kafka input and get rid of the default one whatsoever.
Steps to Reproduce (for bugs)
Create any Kafka input.
Kafka consumer will connect with consumer group id graylog2.
Context
If you have more than one Graylog setup inside a company and someone else connects to the same Kafka topic it might be troublesome. Also some ops teams may not allow generic customer group ids like graylog2.
Your Environment
Graylog Version:
2.2.3
The text was updated successfully, but these errors were encountered:
I can confirm running into the problem in real life. Another team subscribed to our kafka and "stole" some of our logging before we caught on to the problem and switched the inputs off.
In addition it would make migrating a team of a shared graylog to a dedicated one a lot easier if two graylog instances could both consume from the same kafka in parrallel for a while to build up some logging history.
Expected Behavior
Be able to define a customer group id for Kafka inputs.
Current Behavior
There is a hardcoded customer group id set to graylog2.
Possible Solution
Allow user to supply the name through UI for each Kafka input and get rid of the default one whatsoever.
Steps to Reproduce (for bugs)
Context
If you have more than one Graylog setup inside a company and someone else connects to the same Kafka topic it might be troublesome. Also some ops teams may not allow generic customer group ids like graylog2.
Your Environment
2.2.3
The text was updated successfully, but these errors were encountered: