Specifically for the conn.log, that is the event handler in which the log file entries are written with Log::write(). You can look at where that's done in base/protocols/conn/main.bro. For other logs, Log::write() may get called from other event handlers depending on what the log file is supposed to convey. E.g. in base/protocols/http/main.bro, you'll see that Log::write() can get called as soon as an HTTP response body is seen, it doesn't wait for the connection_state_remove event, but it does use it as a fallback for writing out incomplete request/response pairs. In the case you are extending an existing logging stream, you can update your new logging state (record fields marked with &log) in any event handler that you expect to occur before the handlers that do Log::write(). In the case you are designing your own custom logging stream, you get full control over which event handlers you want to update your logging state and which ones you want to write to your log stream. For an example see: http://www.bro-ids.org/documentation/logging.html#adding-streams +Jon