Chad,
The custom Processor would just need to be emitting a Provenance RECEIVE event
(if the processor receives data as a new FlowFile)
or a FETCH event (if the processor is changing the contents of an existing
FlowFile by pulling data from an external source).
The framework will then handle
Hey Mark,
I see. That makes sense why I didn’t see metrics for flowfiles coming from
GenerateFlowFile processor.
When using custom NARs to consume from external sources, is there any code that
needs to be added to the NAR so the processor’s metrics are reported in this
category or does NiFi
Chad,
It represents any FlowFile that was received from an external source. This
could be via
Site-to-Site or could be from something like GetHTTP, FetchSFTP, etc. It
correlates
to any RECEIVE or FETCH provenance events.
If you go to the Summary table (menu in the top right / Summary) and then
I was looking for some clarification on the AmbariReportingTask, and
specifically the metrics FlowFilesReceivedLast5Minutes and
BytesReceivedLast5Minutes.
Looking at the configuration for AmbariReportingTask, it has the property
‘Process Group ID’ and explains that if left blank, the root
