# Spicy & logging framework **URL:** \ **Category:** Zeek\ **Created:** [December 2, 2015, 3:29am UTC](https://community.zeek.org/t/spicy-logging-framework/3926 "2015-12-02T03:29:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Troy\_Jordan](https://avatars.discourse-cdn.com/v4/letter/t/ecae2f/32.png) [@Troy\_Jordan](https://community.zeek.org/u/Troy_Jordan)\ **Post date:** [December 2, 2015, 3:29am UTC](https://community.zeek.org/t/spicy-logging-framework/3926/1 "2015-12-02T03:29:23Z")
Hello, Is there a special method for invoking the Bro logging framework when writing protocol analyzers in Spicy? In my case, I've disabled the legacy parser (modbus) to not clash with the Spicy parser I'm writing. Where should the code for invoking the logging framework reside in this case? Thanks. - Troy ---
**Author:** ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)\ **Post date:** [December 2, 2015, 4:28am UTC](https://community.zeek.org/t/spicy-logging-framework/3926/2 "2015-12-02T04:28:14Z")
The model is to keep doing that from Bro script-land, just as with the standard analyzers as well. So you'd trigger the events from Spicy, via the \*.evt files, and then write Bro script code to create your log file. If your new Spicy-based Modbus parser generated exactly the same events as the legacy one, you'd automatically get the same log file as well. If not (which I deem more likely :-), you'll have to write new scripts replacing the current ones. Robin ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\ **Post date:** [May 6, 2022, 3:43pm UTC](https://community.zeek.org/t/spicy-logging-framework/3926/3 "2022-05-06T15:43:15Z")