t; -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Tuesday, 11 April 2017 4:02 AM
> To: users@nifi.apache.org
> Subject: Re: Logging changes to workflow
>
> Juan,
>
> They were introduced in https://issues.apache.org/jira/browse/NIFI-986
e exists a
> class specifically for reporting configuration changes?
>
> Regards John
>
> -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Tuesday, 11 April 2017 4:02 AM
> To: users@nifi.apache.org
> Subject: Re: Logging changes to workflow
>
al Message-
From: Joe Witt [mailto:joe.w...@gmail.com]
Sent: Tuesday, 11 April 2017 4:02 AM
To: users@nifi.apache.org
Subject: Re: Logging changes to workflow
Juan,
They were introduced in https://issues.apache.org/jira/browse/NIFI-986
I don't know if there is a reporting task which leverage
Juan,
They were introduced in https://issues.apache.org/jira/browse/NIFI-986
I don't know if there is a reporting task which leverages this yet but
the key classes to notice are here:
ReportingTask [1]
EventAccess [2]
>From that one can access the list of changes from a given offset onward.
Hi Joe / all,
" we make it available via reporting tasks "
What reporting task is that? I've looked at NIFI 1 available reporting
tasks and I don't see anything that would let me export "flow configuration
history".
Coincidentally we are having to meet similar requirement.
Our solution was to
John
To build on Andrew's comments there is already a very significant
amount of audit data made available for flow changes. We store this
in an audit database so we can drive some user experiences off it and
we make it available via reporting tasks so one could report this
information to an
John, the Flow Configuration History menu item already captures it. Does it
look like a fit?
Andrew
On Sun, Apr 9, 2017, 10:50 PM HARRIOTT, John
wrote:
> Is it possible to log changes to a workflow so they can be captured by a
> central logging/auditing capability