Hi Simon/Team. Please provide some good example of tail processor.
I need some example for " Rolling Filename Pattern". Also, as per my knowledge TailFile processor is used for tailing local file then what does location attribute signifies, if I set it to remote. Regards, Sourav Gulati -----Original Message----- From: Simon Ball [mailto:[email protected]] Sent: Wednesday, April 20, 2016 2:27 PM To: [email protected] Subject: Re: Reg: Tailing a remote file Site-to-site is in pretty much every version of nifi released under apache. > On 20 Apr 2016, at 10:48, Sourav Gulati <[email protected]> wrote: > > Thanks Simon. Which version of Nifi support site to site? > > Regards, > Sourav Gulati > > -----Original Message----- > From: Simon Ball [mailto:[email protected]] > Sent: Wednesday, April 20, 2016 1:28 PM > To: [email protected] > Subject: Re: Reg: Tailing a remote file > > The best way to do this would be to run a nifi agent on the remote system, > using the TailFile processor, and then use site-to-site to get that into your > core nifi. > > Simon > > >> On 20 Apr 2016, at 09:49, Sourav Gulati <[email protected]> wrote: >> >> Hi Team, >> >> We want to process logs from a file which is getting updated continuously on >> remote system. >> >> What is the best way to do that in NiFi? >> >> Regards, >> Sourav Gulati >> >> >> ________________________________ >> >> >> >> >> >> >> NOTE: This message may contain information that is confidential, >> proprietary, privileged or otherwise protected by law. The message is >> intended solely for the named addressee. If received in error, please >> destroy and notify the sender. Any use of this email is prohibited when >> received in error. Impetus does not represent, warrant and/or guarantee, >> that the integrity of this communication has been maintained nor that the >> communication is free of errors, virus, interception or interference. > > ________________________________ > > > > > > > NOTE: This message may contain information that is confidential, proprietary, > privileged or otherwise protected by law. The message is intended solely for > the named addressee. If received in error, please destroy and notify the > sender. Any use of this email is prohibited when received in error. Impetus > does not represent, warrant and/or guarantee, that the integrity of this > communication has been maintained nor that the communication is free of > errors, virus, interception or interference. > ________________________________ NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
