Hey, all. I wanted to let everyone know that I just released a brand new version of Burrow that resolves a lot of issues that have been collecting. We’ve been working hard on this internally for the last few months, and it’s been running in production at LinkedIn for a few weeks now. So I’m happy to announce that I’ve just released version 1.0.0
https://github.com/linkedin/Burrow/releases/latest First off, from a user point of view, there’s a few big things: 1) The releases are now built for Linux, Windows, and OS X and you can download them directly at https://github.com/linkedin/Burrow/releases/latest 2) The Docker image is now built and pushed as toddpalino/burrow 3) The config has changed significantly. Please review https://github.com/linkedin/Burrow/wiki/Configuration For features, there’s a lot of change: 1) Full support for topic deletion in Kafka 2) Full support for both TLS and SASL 2) Offset handling and evaluation is much cleaner and less prone to missing commits and false alerts 3) Lag numbers are now intuitive - if a consumer stops, the lag will increase >From a developer point of view, this is a ground-up rewrite of Burrow: 1) Everything is modular, making it easier to add modules for custom consumer types, or notifiers 2) The internals have a significant amount of test coverage, meaning it’s easier to know when a change will break things 3) CI is finally set up for testing on every PR, and for building releases 4) Burrow can be started as a library. This will make it easier to build applications that wrap it for custom configuration or logging systems. There’s a number of things to be worked on still, and I’ll be starting these as I have time: 1) Metrics for Burrow itself 2) Making it easier to provide custom modules without a fork 3) Better docs for setting up notifiers, and more sample configs and templates As always, please let me know if there are any issues. I’ve set up #burrow on the Confluent Community Slack for discussion, though I will probably be setting up Gitter on the project directly as well. And for bugs, there are always the Github issues, or PRs for contributing! -Todd -- *Todd Palino* Senior Staff Engineer, Site Reliability Data Infrastructure Streaming linkedin.com/in/toddpalino
