zeek/scripts/base
Johanna Amann 58613f0313 Introduce new c$failed_analyzers field
This field is used internally to trace which analyzers already had a
violation. This is mostly used to prevent duplicate logging.

In the past, c$service_violation was used for a similar purpose -
however it has slightly different semantics. Where c$failed_analyzers
tracks analyzers that were removed due to a violation,
c$service_violation tracks violations - and doesn't care if an analyzer
was actually removed due to it.
2025-06-04 12:07:13 +01:00
..
files Copy timestamp from file object 2024-05-17 15:03:06 +02:00
frameworks Introduce new c$failed_analyzers field 2025-06-04 12:07:13 +01:00
misc Fix errors from rst linting on the generated docs 2025-01-24 11:41:36 -07:00
packet-protocols Add analyzer registration from VLAN to VNTAG 2025-03-18 11:51:27 -07:00
protocols spicy-redis: Separate error replies from success 2025-05-27 09:31:25 -04:00
utils Fix errors from rst linting on the generated docs 2025-01-24 11:41:36 -07:00
init-bare.zeek Merge remote-tracking branch 'origin/topic/awelzel/4177-4178-custom-event-metadata-part-2' 2025-06-02 17:33:22 +02:00
init-default.zeek spciy-redis: Bring Redis analyzer into Zeek proper 2025-05-27 09:28:12 -04:00
init-frameworks-and-bifs.zeek Minor comment tweaks for init-frameworks-and-bifs.zeek 2024-10-18 09:56:29 -07:00
init-supervisor.zeek Establish a separate init script when using the supervisor 2021-07-08 13:12:53 -07:00