Also, you will be able to create the archetype project outside of the
metron code tree. Although the root parent pom should still be pointing to
*into* metron.
My goal is to eliminate any necessity to fork metron is possible, you
shouldn’t have to unless you really want to.
On May 9, 2017 at 13
Yes, METRON-777 is the first step to resolving that. The follow on, that
I’ll be putting up as a follow up soon is METRON-942 ( Rest interface for
installing, querying and uninstalling extensions ).
As of METRON-777, every parser is a plugin ( or extension as I am calling
them ) and has been refact
Correct me if I’m wrong, but we currently have a lot of hard-coded
configuration files with the standard telemetry (yaf, bro, snort) included, but
no consistent way to add additional telemetry configuration where needed?!
I.e. we have
-
/usr/metron//config/zookeeper/[enrichments|parsers|indexing
