I can't speak to whether or not it is 'needed', but I have had desire to use it
in the past... The only thing preventing me from doing it was the fact that
Broker is currently a fast moving target.
Generally speaking, I was wanting to do it so that I could save state between
cluster restarts (s
stuff in a while since
I'm eagerly awaiting your rewrite of the Broker APIs :)
From: Matthias Vallentin [matth...@vallentin.net] on behalf of Matthias
Vallentin [vallen...@icir.org]
Sent: Monday, July 25, 2016 11:25 AM
To: Hosom, Stephen M
Cc: Siwek
Battelle's test cluster is currently on Master. I'll forward any issues that we
have.
-Original Message-
From: bro-dev-boun...@bro.org [mailto:bro-dev-boun...@bro.org] On Behalf Of
Robin Sommer
Sent: Monday, May 15, 2017 11:18 AM
To: Vlad Grigorescu
Cc: bro-dev@bro.org
Subject: Re: [Br
I too would miss the commit / change notifications, however, I think that this
can be set up in GitHub in some way. We use Slack / Email internally for commit
notifications. For Slack, we use webhooks to send notifications.
Email commit notifications are actually a builtin integration in GitHub
Well... in looking at how I set this up internally, I now realize that this
feature is being EOL and will no longer work as of January 31, 2019. I guess it
would have to be webhooks.
On 5/16/18, 11:30 AM, "bro-dev-boun...@bro.org on behalf of Hosom, Stephen M"
wrote:
I too
I bumped into a limitation that was a little frustrating to work around with
the config framework.
It is inconvenient that values stored in files read by adding to
Config::config_files are not available within the bro_init event. After
reviewing how the Config framework works, I understand why
oting for hours.
Maybe it would be worthwhile to just add a note in the documentation for the
config framework about it and leave it at that?
From: Azoff, Justin S
Sent: Tuesday, October 30, 2018 3:41:00 PM
To: Hosom, Stephen M
Cc: bro-dev@bro.org
Subject: Re:
I've been working on an application that will fire a large volume of events
into bro through broker. Basically, I want to fire events into Broker and load
balance them across a pool of workers without the need for more than one worker
to handle the same event.
I'm having difficulty determining
