Skip to content

Testing Group

Christian Kreibich edited this page Jun 22, 2023 · 5 revisions
Clone this wiki locally

The goal of the testing subgroup is to stress-test new versions of Zeek with real live traffic from a variety of environments to identify problems and bugs early, to ensure that new Zeek releases are stable and ready for the Zeek community.

Requirements For Participation

The Testing subgroup is seeking members who have spare systems/taps and the cycles to occasionally run development versions of Zeek, release candidates or pre-releases on their live institutional traffic in parallel to their production Zeek infrastructure. You, as a member of the testing subgroup, will report back to the developers if you are seeing smooth stable runs or if new or previously unknown bugs manifest.

You’d be the one to identify issues and report back to the developers, who will do their best to fix them as soon as possible. We don’t anticipate too many requirements from the Dev team. Occasionally developers may ask you to test some specific branch. Mostly you’d end up running what will become the next stable release. You are just needed to report back performance numbers or other problems you notice.

Members of the Testing group should generally be aiming to run a current release version on their operational site (optimally the current feature release, but the LTS release also is fine), so that they can compare the behavior with the test version running in parallel.

(See blog post for more information)

Ways to get involved in the group:

** Application for Participation -


More information