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

Datastreams for zeek should be inside the logs-* naming #1

Closed
philippkahr opened this issue Jan 15, 2022 · 7 comments
Closed

Datastreams for zeek should be inside the logs-* naming #1

philippkahr opened this issue Jan 15, 2022 · 7 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request helper scripts Requires work to the helper scripts.

Comments

@philippkahr
Copy link

philippkahr commented Jan 15, 2022

Hi

I just discovered this great repository. I personally think that when using datastreams the naming convention should be logs-zeek-default. This would follow our datastream recommendations for type-dataset-namespace.

By placing the index with starting logs it will show up automatically within the logs stream and the security pages and all other sorts of places within Kibana.

@keithjjones
Copy link
Collaborator

keithjjones commented Jan 15, 2022

Thanks!

I looked this over and don't understand what I'm losing if I don't name data streams this way, but I think I'd have to remove functionality from zeek2es to match this naming convention.

The way I'm naming things is pretty important to how I'm processing things down the line for my research. I have the index/datastream names this way so Zeek formats can change over time, which happens a lot in my research. If I put all conn logs in logs-zeek-conn I won't be able to change the mapping for two different conn logs with different formats.

@keithjjones
Copy link
Collaborator

This functionality should exist already if you use the -d and -i switches to put it in your logs-zeek-conn data stream.

@keithjjones
Copy link
Collaborator

I clarified the -i option in the readme and the zeek2es help screen with -h.

@keithjjones
Copy link
Collaborator

keithjjones commented Jan 15, 2022

Here is a new script to automate what I talked about above: https://github.com/corelight/zeek2es/blob/working/process_logs_as_datastream.sh

@keithjjones
Copy link
Collaborator

keithjjones commented Jan 15, 2022

TIL you can make a data stream by naming a regular index log-zeek-conn-something! I did not know that was possible! So for that instance, you don't even need the -d option if you do not want zeek2es to automatically set up your index rollover based on size. Just use -i log-zeek-conn or whatever you want to call your data stream with that log-zeek prefix.

@keithjjones
Copy link
Collaborator

keithjjones commented Jan 18, 2022

I added another helper script and some documentation: https://github.com/corelight/zeek2es/tree/master#helperscripts These should do what you describe above.

@keithjjones keithjjones self-assigned this Jan 18, 2022
@keithjjones keithjjones added documentation Improvements or additions to documentation enhancement New feature or request helper scripts Requires work to the helper scripts. labels Jan 18, 2022
@keithjjones
Copy link
Collaborator

Since the newest updates addressed this issue, I'm closing it now. Please reopen if you think I missed the mark. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request helper scripts Requires work to the helper scripts.
Projects
None yet
Development

No branches or pull requests

2 participants