Hi Fred, I have used the reporting task with specific event types listed, but I've not run into issues personally.
I am curious if you have tried looking for more common event types, such as RECEIVE, CONTENT_MODIFIED, or ATTRIBUTES_MODIFIED? EXPIRE events only fire when FlowFiles get aged off from a Connection due to not being processed within the Connection's "FlowFile Expiration" threshold, and DOWNLOAD events are only triggered when a user downloads the contents of the FlowFile to look at it manually. So both of these are fairly rare events. RECEIVE, ATTRIBUTES_MODIFIED, and CONTENT_MODIFIED, on the other hand, will generally happen constantly. Thanks -Mark On Oct 4, 2017, at 4:50 PM, Fred S <fs9387...@gmail.com<mailto:fs9387...@gmail.com>> wrote: Dear community. I'm currently trying to set up a SiteToSiteProvenanceReportingTask to keep track of DOWNLOAD provenance events. If I set it up without any filters at all everything gets sent to my dedicated NiFi instance for handling these messages. When I set a filter in the "Event Type" property (I've tried "DOWNLOAD" and "DOWNLOAD, EXPIRE") - nothing. I've been looking around for anyone experiencing a similar issue, without any luck. Have anyone else set this up successfully without having to log *all* provenance events? Due to the number of flowfiles I have flying by each day it would not be feasible to go with that approach. I see this issue on both NiFi 1.3.0 and 1.4.0. For what it's worth I've also tried to accomplish this both with and without security/ssl. If anyone else needs any additional information about my setup, please let me know. All the best, Fred
