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

Feature Request: Index based on "Community ID" #966

moshekaplan opened this issue Nov 27, 2018 · 4 comments


Copy link

commented Nov 27, 2018

Corelight (the company behind Bro/Zeek) published a project describing a "Community ID" - a separate specification for generating a likely-unique identifier for a network connection. This is implemented for both Bro/Zeek and Suricata. It would be great if moloch also supported the Community ID, so as to ease cross-referencing between Bro logs and Suricata logs with the network traffic indexed by moloch.

For more information, see and


This comment has been minimized.

Copy link

commented Nov 27, 2018

was already on the list in my head, thanks for opening an issue


This comment has been minimized.

Copy link

commented Jan 3, 2019

I am looking forward to this feature. Thanks!


This comment has been minimized.

Copy link

commented Jan 4, 2019

Looking forward to this as well. Will be great to have a hard pivot between Moloch, Bro and Suricata data.

awick added a commit that referenced this issue Jan 7, 2019

@awick awick closed this Jan 7, 2019


This comment has been minimized.

Copy link

commented May 16, 2019

I'm very late to the party here, but wanted to say thanks to everyone for adding this! I've added a link to in the known-implementations section over on the spec page:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
5 participants
You can’t perform that action at this time.