[ 
https://issues.apache.org/jira/browse/NIFI-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518534#comment-16518534
 ] 

ASF GitHub Bot commented on NIFI-5325:
--------------------------------------

Github user bbende commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2805#discussion_r196906833
  
    --- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
    @@ -327,6 +327,10 @@
                 <version>1.7.0-SNAPSHOT</version>
                 <scope>test</scope>
             </dependency>
    +        <dependency>
    +            <groupId>com.github.palindromicity</groupId>
    +            <artifactId>simple-syslog-5424</artifactId>
    +        </dependency>
    --- End diff --
    
    Since this transitively brings in antlr-runtime (I think) then we probably 
need to account for that in the NAR and assembly LICENSE/NOTICE. 
    
    From a quick glance it looks like antlr is BSD 3-Clause so it probably goes 
in the LICENSE files with the verbiage like: "The binary distribution of this 
product bundles 'antlr-runtime' which is available under a "3-clause BSD" 
license."


> Need a Syslog Parser that fully supports the 5424 Spec
> ------------------------------------------------------
>
>                 Key: NIFI-5325
>                 URL: https://issues.apache.org/jira/browse/NIFI-5325
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Otto Fowler
>            Assignee: Otto Fowler
>            Priority: Major
>
> from NIFI-5139
> "The Structured Data as described in 
> [https://tools.ietf.org/html/rfc5424#section-6.3] are not read by Nifi.
>  
> I suggest the SD to be put in attributes, prefixed by the ID:
> [exampleSDID@32473 iut="3" eventSource="Application" eventID="1011"]
> to become 3 attributes
>  * exampleSID@32473-iut = 3
>  * exampleSID@32473-eventSource=Application
>  * exampleSID@32473-eventID=1011
>  
> This could be useful to preprocess RFC5424 message, prioritize or route them."
>  
> Nifi should a have a parser to fully support the spec and structured data.
> Since integrating it, and special casing the existing parser would 
> simnifically complicate that processor and move it from it's least common 
> denominator goal, it should be a new parser
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to