[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057747#comment-16057747
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/530#discussion_r123291122
--- Diff: metron-analytics/metron-maas-service/README.md ---
@@ -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 --
Yes that is my thinking. They, along with JSONMap provide base
capabilities to be extended by other parsers, or to be used with configurations
to make they themselves useful. So if we added an XML or scripting parser, it
would go in here as well.
The extensions - in the context of these types - are the bundling of
specific configurations of these base parsers ( indexing, parser, enrichment,
ES ) into a single installable unit.
You could also do this manually by pushing configurations to the right
places in zookeeper and changing ambari etc, and you can still do this in a
post 777 world.
Extensions also give a project structure for implementing and executing
unit and integration tests, on even configuration only parsers ( SEE: YAF,
SQUID ). This I think should be the recommended way, even the supported way
for production.
Along with METRON-942 that is.
> Create a plugin system for Metron based on 'NAR'
> ------------------------------------------------
>
> Key: METRON-777
> URL: https://issues.apache.org/jira/browse/METRON-777
> Project: Metron
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> The success of the Metron project will be greatly dependent on community
> participation, and with that the ability to adapt and extend Metron without
> having to maintain a fork of the project.
> As organizations and individuals look to extend the Metron system with custom
> parsers, enrichments, and stellar functions that may be proprietary in
> nature, the ability to develop and deploy these extensions outside the Metron
> code base is critically important.
> To that end, and after community discussion and proposal we create or
> formalize the 'plugin' development story in Metron.
> The proposal is to adapt the Apache Nifi NAR system for use in Metron. This
> will provide the system with:
> * archetype(s) for developer projects and independent development
> * defined packaging and metadata for 'plugin' products
> * loading and instantiation with classloader isolation capabilities
> * removing the necessity for shading plugin jars
> These capabilities will also enable other features, such as plugin lifecycle,
> plugin configuration+redeployment, and other things.
> The plugin archetypes and their installation will be a followon
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
