Re: [Bro-Dev] Broker port status

> On Mar 9, 2018, at 8:24 AM, Azoff, Justin S wrote: > > Ah.. I grabbed the latest commit from the wrong checkout and was using a > commit from a few weeks ago. > Ok.. running the latest commit now (105fc386ef0f65a91839706641abae664c7f3e49) Have noticed a problem where

Re: [Bro-Dev] Broker port status

> On Mar 8, 2018, at 6:32 PM, Jon Siwek wrote: > > Yeah, I realized that and fixed it yesterday. Have you pulled the > latest commits from the topic/actor-system branch? > > - Jon Ah.. I grabbed the latest commit from the wrong checkout and was using a commit from a

Re: [Bro-Dev] Broker port status

On Thu, Mar 08, 2018 at 13:28 -0600, you wrote: > * Rename "proxy" nodes? "compute" maybe? > (1) , , Seems fine to deprecate these > now. Agree. > (2) Communication framework scripts. It's awkward to deprecate stuff > here since they internally will be using what is deprecated. I think

Re: [Bro-Dev] Broker port status

On Thu, Mar 8, 2018 at 6:11 PM, Azoff, Justin S wrote: >> redef Known::use_host_store = F; >> redef Known::use_cert_store = F; >> redef Known::use_device_store = F; >> redef Known::use_service_store = F; > but if you load the script first, the > > @if (

Re: [Bro-Dev] Broker port status

> On Mar 8, 2018, at 5:46 PM, Jon Siwek wrote: > > On Thu, Mar 8, 2018 at 5:07 PM, Azoff, Justin S wrote: > >> One thing I notice is that the traffic to/from the manager box and cpu has >> increased quite a bit. >> >> Ignoring the large CPU spikes

Re: [Bro-Dev] Broker port status

On Thu, Mar 8, 2018 at 5:07 PM, Azoff, Justin S wrote: > One thing I notice is that the traffic to/from the manager box and cpu has > increased quite a bit. > > Ignoring the large CPU spikes from building the new branch just before the > switch at 15:30, the overall cpu

Re: [Bro-Dev] Broker port status

On Thu, Mar 8, 2018 at 2:18 PM, Azoff, Justin S wrote: >> (1) , , Seems fine to deprecate these >> now. > > I'm fine with it going away, but there needs to be some sort of replacement > for , > minimally a how-to for porting existing scripts to something else. The

Re: [Bro-Dev] Broker port status

> On Mar 8, 2018, at 1:28 PM, Jon Siwek wrote: > > Hi all, this is just a status update on porting Bro to use the new > Broker communication system. I'd say the topic/actor-system branch is > now functionally complete with still a few weeks left of internal >

[Bro-Dev] Broker port status

Hi all, this is just a status update on porting Bro to use the new Broker communication system. I'd say the topic/actor-system branch is now functionally complete with still a few weeks left of internal cleanup/improvements. Open questions: * Rename "proxy" nodes? The previous idea was to call