We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
By default Zeek stores logs in a plain text that if exported to a SIEM or log aggregator require additional parsing and sorting.
Zeek does have the ability to format logs as structured JSON making importing much easier.
Zeek Logging Framework Zeek to Splunk Example
The text was updated successfully, but these errors were encountered:
For anyone who comes here via Google search, if doing to manually, it is as simple as adding the following line:-
# Output to JSON @load policy/tuning/json-logs.zeek
at location: /usr/local/share/zeek/policy/tuning/defaults/__load__.zeek.
/usr/local/share/zeek/policy/tuning/defaults/__load__.zeek
Side note, I tried editing the location /opt/zeek/share/zeek/site/local.zeek directly, but, for whatever reason, JSON logging wasn't getting enabled
/opt/zeek/share/zeek/site/local.zeek
Considering how easy it is to enable JSON logging, it should be easy to do via GUI as well.
Sorry, something went wrong.
No branches or pull requests
By default Zeek stores logs in a plain text that if exported to a SIEM or log aggregator require additional parsing and sorting.
Zeek does have the ability to format logs as structured JSON making importing much easier.
Zeek Logging Framework
Zeek to Splunk Example
The text was updated successfully, but these errors were encountered: