[ https://issues.apache.org/jira/browse/NIFI-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Zhurakousky updated NIFI-1170: ----------------------------------- Fix Version/s: 1.1.0 > TailFile "File to Tail" property should support Wildcards > --------------------------------------------------------- > > Key: NIFI-1170 > URL: https://issues.apache.org/jira/browse/NIFI-1170 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework > Affects Versions: 0.4.0 > Reporter: Andre > Fix For: 1.1.0 > > > Because of challenges around log rotation of high volume syslog and app > producers, it is customary to logging platform developers to promote file > variables based file names such as DynaFiles (rsyslog), Macros(syslog-ng)as > alternatives to getting SIGHUPs being sent to the syslog daemon upon every > file rotation. > (To certain extent, used even NiFi's has similar patterns, like for example, > when one uses Expression Language to set PutHDFS destination file). > The current TailFile strategy suggests rotation patterns like: > {code} > log_folder/app.log > log_folder/app.log.1 > log_folder/app.log.2 > log_folder/app.log.3 > {code} > It is possible to fool the system to accept wildcards by simply using a > strategy like: > {code} > log_folder/test1 > log_folder/server1 > log_folder/server2 > log_folder/server3 > {code} > And configure *Rolling Filename Pattern* to * but it feels like a hack, > rather than catering for an ever increasingly prevalent use case > (DynaFile/macros/etc). > It would be great if instead, TailFile had the ability to use wildcards on > File to Tail property -- This message was sent by Atlassian JIRA (v6.3.4#6332)