Supports Expression Language: trueRolling Filename Pattern | | | If the file to tail "rolls over" as would be the case with log files, this filename pattern will be used to identify files that have rolled over so that if NiFi is restarted, and the file has rolled over, it will be able to pick up where it left off. This pattern supports wildcard characters * and ?, it also supports the notation ${filename} to specify a pattern based on the name of the file (without extension), and will assume that the files that have rolled over live in the same directory as the file being tailed. The same glob pattern will be used for all files. |
Base directory | | | Base directory used to look for files to tail. This property is required when using Multifile mode. Supports Expression Language: true |
Initial Start Position | Beginning of File | - Beginning of Time
 - Beginning of File
 - Current Time

| When the Processor first begins to tail data, this property specifies where the Processor should begin reading data. Once data has been ingested from a file, the Processor will continue from the last point from which it has received data. |
State Location | Local | - Local
 - Remote

| Specifies where the state is located either local or cluster so that state can be stored appropriately in order to ensure that all data is consumed without duplicating data upon restart of NiFi |
Recursive lookup | false | | When using Multiple files mode, this property defines if files must be listed recursively or not in the base directory. |
Lookup frequency | 10 minutes | | Only used in Multiple files mode and Changing name rolling strategy. It specifies the minimum duration the processor will wait before listing again the files to tail. |
Maximum age | 24 hours | | Only used in Multiple files mode and Changing name rolling strategy. It specifies the necessary minimum duration to consider that no new messages will be appended in a file regarding its last modification date. This should not be set too low to avoid duplication of data in case new messages are appended at a lower frequency. |
Relationships:
Name | Description |
---|
success | All FlowFiles are routed to this Relationship. |
Reads Attributes:
None specified.Writes Attributes:
Name | Description |
---|
tailfile.original.path | Path of the original file the flow file comes from. |
State management:
Scope | Description |
---|
LOCAL, CLUSTER | Stores state about where in the Tailed File it left off so that on restart it does not have to duplicate data. State is stored either local or clustered depend on the <File Location> property. |
Restricted:
Required Permission | Explanation |
---|
read filesystem | Provides operator the ability to read from any file that NiFi has access to. |
Input requirement:
This component does not allow an incoming relationship.System Resource Considerations:
None specified.