BTW I ended up using the Footer property in MergeContent and it worked wonderfully with no regex involved. ... View more

Awesome! Yes! This is what I was looking for I think ... View more

I was thinking that too and Hellmar's answer gave me a clue as how to do it but using ReplaceText to add a newline doesn't allow me to specify "Add a new line right after a specific bin of events" or "Add a new line right before this first line in this bin of events" but rather it allows me to use regex to find keywords in the data (I am putting a newline before the timestamp which works but also adds an extra line after every event). Is there a way to specify "put a newline at the end of this bin of events before the append happens" ? ... View more

Thank you for this advice, but it requires me to use regex. The issue with this is that the end character(s) of events that may be coming in will be different for the type of setup we are using. I guess I can try to search for the start of the timestamp and try to put the "\n" before it which I will try. Its unfortunate and seems like a gross oversight if this append features exists this way, combining the previous event and appended event together. I was hoping there was a solution that was integrated in the technology for this instead of a workaround. ... View more

I know this was from awhile ago but I just noticed with this solution, the appended data starts right at the end of the previous event causing data loss cause two events get smooshed together. Do you have this issue when you do this and how do you fix it? Example: Apr 11 05:00:39 fw01 /kernel: KERN_ARP_ADDR_CHANGE: arp info overwritten for 10.11.x.x from 00:xx:xx:xx:xx:cd to 00:xx:xx:xx:xx:a3Apr 11 05:00:39 fw01 /kernel: KERN_ARP_ADDR_CHANGE: arp info overwritten for 10.11.x.x from 00:xx:xx:xx:xx:a3 to 00:xx:xx:xx:xx:cd ... View more

Hey Bryan That was it! If you check out the tutorial at https://community.hortonworks.com/articles/56341/getting-started-with-minifi.html the wording makes it seem to me like we were meant to put in the IP address for the sending server. Thank you so much for your help. A week and half to figure this out. ... View more

So I think perhaps theres some confusion. foo.xyz.abc.com is the url of the location of the receiving server and of course, 8080/nifi is added to access the nifi interface 192.168.x.x is the IP address of the sending server. They are different values and should be. In response to your comment: If nifi.web.http.host and nifi.remote.input.host are the same in your nifi.properties, then you can ignore my previous comment. They are not the same - in fact, nifi.web.http.host is blank and when I put the same value as nifi.remote,input.host, the receiving servers Nifi UI does not work anymore (as expected) It is interesting to note that I was actually able to get Nifi to talk to itself through localhost using these values nifi.remote.input.host=localhost nifi.remote.input.secure=false nifi.remote.input.socket.port=10000 nifi.remote.input.http.enabled=true nifi.remote.input.http.transaction.ttl=30 sec I think my next step is to install Nifi on another server than my sending server and try to send to my receiving server to try to figure out which server is the problem child. ... View more