[Bro-Dev] #483: Logging framework using wrong name.

[Bro Tracker]

#483: Logging framework using wrong name.
---------------------+--------------------
 Reporter:  seth     |      Owner:  robin
     Type:  Problem  |     Status:  new
 Priority:  High     |  Milestone:  Bro1.6
Component:  Bro      |    Version:
 Keywords:           |
---------------------+--------------------
 When the logging framework creates filters, it has a problem with enums in
 modules.  If you do this:

 {{{
 module Notice;

 export {
     redef enum Log::ID += { FOOBAR };
 }

 event bro_init()
     {
     Log::create_stream(FOOBAR, [$columns=XYZ]);
     }
 }}}

 If you leave it alone and don't create an output stream, it should be
 pulling the default path (file) name from the stream ID but in the case
 above it would end up using the path name "Notice" because it's not
 dealing with modules correctly.  The full value for the enum is
 Notice::FOOBAR.

 I think it should just take the actual enum name without the module
 because in most cases it would result in redundantly named log files.

-- 
Ticket URL: <http://tracker.bro-ids.org/bro/ticket/483>
Bro Tracker <http://tracker.bro-ids.org/bro>
Bro Issue Tracker