Hi James,
you might want to check the official user guide
https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#data_provenance. In
case you have specific questions, feel free to reach out to me directly!
Best, Lars
On 26 May 2023 12:20:38 CEST, James wrote:
>Hi again
>
>It definitely
Hi again
It definitely could be a training issue on my part, working with Nifi for
so long and STILL figuring things out and finding new cool things to try.
My methodology is more about routing all errors (as an example) to a single
point (processor) so there's 1 log file to monitor, and having a
Hi folks, I think you can obtain the same information via provenance. Or am I
mssing something? It sounds to me like you want to do manual debugging instead
of automizing it, so provenance should be easily accessible. Enjoy your day and
take care! Best, Lars
On 26 May 2023 11:21:13 CEST, James
Hi
This would honestly make life SO much easier!
I've worked around this by adding my own attributes that can get logged in
a central "LogMessage" processor, but even that can prove tricky sometimes.
And this solution would be so much cleaner.
Just my 2c
thanks
James
On Thu, May 25, 2023 a
In a large dataflow with multiple processors, it will help identifying which
processor routed flowfile to failure relationship.
https://community.cloudera.com/t5/Support-Questions/NiFi-origin-processor-name-or-id-as-attribute/m-p/175408
[image005]
Deepak Reddy | Data Engineer
IT Centers of Ex
