metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ottobackwards <>
Subject [GitHub] metron pull request #530: METRON-777 Metron Extension System and Parser Exte...
Date Wed, 21 Jun 2017 20:38:21 GMT
Github user ottobackwards commented on a diff in the pull request:
    --- Diff: metron-analytics/metron-maas-service/ ---
    @@ -138,7 +138,7 @@ Now that we have a deployed model, let's adjust the configurations
for the Squid
     * Edit the squid parser configuration at `$METRON_HOME/config/zookeeper/parsers/squid.json`
in your favorite text editor and add a new FieldTransformation to indicate a threat alert
based on the model (note the addition of `is_malicious` and `is_alert`):
    -  "parserClassName": "org.apache.metron.parsers.GrokParser",
    +  "parserClassName": "org.apache.metron.parsers.grok.GrokParser",
    --- End diff --
    As for a general rule -> Parsers the parser file formats, with no understanding of
the content would be the rule.  "There could be any number of systems supported with this
parser with that number of configurations".    Such parsers should also lend themselves to
be extended in code.
    - grok
    - csv
    - json
    - xml
    - scripting
    - binary json
    - protobuf

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message