Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow users to define Kafka customer group id #3976

mwysokin opened this issue Jul 4, 2017 · 3 comments

Allow users to define Kafka customer group id #3976

mwysokin opened this issue Jul 4, 2017 · 3 comments


Copy link

@mwysokin mwysokin commented Jul 4, 2017

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.

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)

  1. Create any Kafka input.
  2. Kafka consumer will connect with consumer group id graylog2.


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:
Copy link

@lpiet lpiet commented Nov 2, 2018

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.

Copy link

@jhaohai jhaohai commented Nov 8, 2018

We have two graylog clusters and need to subscribe logs from the same kafka cluster.

Copy link

@bernd bernd commented Apr 17, 2019

This has been implemented in #5867 and will be part of Graylog 3.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

6 participants