Also, are you using ListenSyslog?
If so you can see the attributes it produces in documentation [1] where it
says "Writes Attributes", or by looking in provenance. I believe it is
syslog.facility
[1]
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenSyslo
Hello Madhu,
If you're looking for a template to show how to create a dynamic property for
RouteOnAttribute to use, I'd suggest checking out this template[1]. It is a
simple template that checks to see if the an attribute matches 'NiFi'.
Also provenance can be a very powerful debugging tool. I
I am getting my log4j logs on facility value 23 ( LOCAL7) how can route
only facility 23 logs for further extraction.
I added RouteonAttribute processor and defined this property :
${facility:contains(23)} but none of them messages getting matched. I am
not sure my defined property is correct. H
Thanks Bryan. Looking forward for the release.
On Fri, Feb 12, 2016 at 10:55 AM, Bryan Bende wrote:
> I believe groovy, python, jython, jruby, ruby, javascript, and lua.
>
> The associated JIRA is here:
> https://issues.apache.org/jira/browse/NIFI-210
>
> There are some cool blogs about them h
-modules.html
Regards,
Matt
From: Bryan Bende
Reply-To:
Date: Friday, February 12, 2016 at 10:55 AM
To:
Subject: Re: Log4j/logback parser via syslog
I believe groovy, python, jython, jruby, ruby, javascript, and lua.
The associated JIRA is here:
https://issues.apache.org/jira/browse/NIFI-210
I believe groovy, python, jython, jruby, ruby, javascript, and lua.
The associated JIRA is here:
https://issues.apache.org/jira/browse/NIFI-210
There are some cool blogs about them here:
http://funnifi.blogspot.com/2016/02/executescript-processor-hello-world.html
-Bryan
On Fri, Feb 12, 2016 at
Thanks Bryan. I will look into ExtractText processor.
Do you know what scripting languages are supported with new processors?
-Madhu
On Fri, Feb 12, 2016 at 9:27 AM, Bryan Bende wrote:
> Hello,
>
> Currently there are no built in processors to parse log formats, but have
> you taken a look at
Hello,
Currently there are no built in processors to parse log formats, but have
you taken a look at the ExtractText processor [1]?
If you can come up with a regular expression for whatever you are trying to
extract, then you should be able to use ExtractText.
Other options...
You could write a
Hi
I am very new to Apache Nifi and just started learning about how to use it.
We have a requirement where we need to parse log4j/logback pattern messages
coming from SyslogAppenders via Syslog udp. I can read the standard syslog
messages, but how can i further extract log4j/logback messages fro