-
Notifications
You must be signed in to change notification settings - Fork 130
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
bring your own zeek #731
Comments
I've done an initial round of work on the 'zeek runner'. Since it's across all 3 of our main dev repos, all of the tests are failing, but I've verified the PR's work with each other on mac & windows. I'll wait until #634 is in, then use that to make the Brim integration tests pass. |
This is part of the brimsec/brim repo side work for #731. Use the -zeekrunner cli option to zqd ( brimdata/zed#718 ), defaulting to the value of environment variable BRIM_ZEEK_RUNNER, else to the zeekrunner included from the zdeps zeek artifact ( brimdata/zeek#23 ).
The attached video shows the complete feature in action as of Brim commit |
A user should be able to use their own Zeek executable & scripts to perform the pcap to zeek log conversion that occurs during pcap ingest.
This feature would enable:
To implement this, we should reorganize how Zeek is launched from Brim zqd. I suggest we use the idea of a "Zeek runner", a command or script that acts as the interface for Zeek to zqd. It's contract with zqd would be:
This is nearly what the 'zeek' script in brimsec/zeek does today, with the exception of the zeek cli arguments that are currently specified in the zqd source.
Brim would allow a user to specify a location to a runner, defaulting to the one we include in zdeps. We can also allow a user to override the runner with an environment variable.
The text was updated successfully, but these errors were encountered: