Description:
This processor monitors its point in the dataflow for
activity and sends a notice when there is a lack of data flowing
through it for some user-specified amount of time; it then sends
another notice when the flow of data resumes.
Modifies Attributes:
Attribute Name |
Description |
inactivityStartMillis |
The time at which Inactivity began, in the form of milliseconds since Epoch. |
inactivityDurationMillis |
The number of milliseconds that the inactivity has spanned. |
Properties:
In the list below, the names of required properties appear
in bold. Any other properties (not in bold) are considered optional.
If a property has a default value, it is indicated. If a property
supports the use of the NiFi Expression Language (or simply,
"expression language"), that is also indicated.
- Threshold Duration
- The amount of time that must elapse before the flow is
considered inactive.
- Default value: 5 min
- Supports expression language: false
- Continually Send Messages
- A Boolean value (true/false), indicating whether to send
inactivity notices continually every time the threshold duration
period elapses until activity is restored. If false, the processor
will send a notice only when the flow first becomes inactive.
- Default value: false
- Supports expression language: false
- Inactivity Message
- The message that will appear as the content of outgoing
FlowFiles that are sent to the inactive relationship.
- Default value:
- Lacking activity as of time: ${now():format('yyyy/MM/dd
HH:mm:ss')}; flow has been inactive for
${inactivityDurationMillis:toNumber():divide(60000)} minutes.
- Supports expression language: true
- Activity Restored Message
- The message that will appear as the content of outgoing
FlowFiles that are sent to the activity.restored relationship.
- Default value:
- Activity restored at time: ${now():format('yyyy/MM/dd
HH:mm:ss')} after being inactive for
${inactivityDurationMillis:toNumber():divide(60000)} minutes.
- Supports expression language: true
- Copy Attributes
- If true, will copy all flow file attributes from the flow file that resumed activity to the newly created indicator flow file.
- Default value: false
- Supports expression language: false
Relationships:
- activity.restored
- FlowFiles containing the content specified by the Activity
Restored Message property follow this relationship when FlowFiles
are routing to the success relationship following a period of
inactivity.
- inactive
- FlowFiles containing the content specified by the
Inactivity Message property follow this relationship when FlowFiles
stop routing to the success relationship for the period of time set
in the Threshold Duration property.
- success
- All incoming FlowFiles follow this relationship.