v1.2.0

• brimcap search: parse -duration argument as a ZSON duration (#244)
• brimcap slice: parse -to and -from arguments as an RFC 3339 timestamp (#243)
• brimcap ts: print timestamps in RFC 3339 format (#243)
• Remove brimcap migrate (#234)

v1.1.2

• Allow Brimcap analyzers to benefit from Zed JSON reader enhancements zed/3124 and zed/3123

v1.1.1

• Fix an issue where pcap index entries for legacy Spaces were not being migrated (#156)

v1.1.0

• Allow expansion of environment variables in Brimcap config YAML (#153)

v1.0.4

• Additions to custom YAML configuration (#148)
  • A root option can be used to specify the Brimcap root location
  • name is now a required part of an analyzer configuration

v1.0.3

• Update legacy Space migration to work with Zed Lake branches (#140, #145)
• Fix an issue where temporary analyzer directories were not being deleted on exit (#137)

v1.0.2

• Fix an issue where legacy Space migration would fail for a custom Data Directory in Brim (#133)

v1.0.1

• Fix an issue where stale packet index entries could cause a failure to extract a flow from another pcap (#128)

v1.0.0

• Include the name of the analyzer process with any warnings & errors it generates (#122)
• Adjust defaults for whether logging during analysis is output as JSON vs. status line (#123)
• Rather than quitting, emit a warning and continue if brimcap analyze fails to read an output file (#125)

v0.0.6

• Move the Geolocation article over from the Brimcap wiki (#104)
• Refactor brimcap analyze to use the new Zed Lake add/commit endpoints and fix a deadlock issue (#110)
• Fix a deadlock issue that was caused by an analyze process writing no records (#115)
• Fix the percentage and byte counts on the command line status updates (#116)
• Drop brimcap load in favor of granular use of brimcap analyze, brimcap index and zapi (#117, #114, #120)