>It looks like the thread skipped over the problem space for the solution space pretty fast
OK, I apologize, it seemed to me from the feedback that the problem was already uncontested. To verify/falsify that was the objective of my previous mail :) >Can you elaborate? Sure. CSV Logs: https://pastebin.com/uwfmRdU7 stdout: https://gist.github.com/blaggacao/d389940ef7b223eebc707096b536967d CSV shows line breaks, STDOUT shows ERROR/FATAL and detail on different lines, not an easy problem to stream-parse reliably (without some kind of a buffer, etc)... El dom., 15 abr. 2018 a las 12:46, Christophe Pettus (<x...@thebuild.com>) escribió: > > > On Apr 15, 2018, at 10:39, David Arnold <dar@xoe.solutions> wrote: > > > > In the light of the specific use case / problem for this thread to be > born, what exactly would you suggest? > > It looks like the thread skipped over the problem space for the solution > space pretty fast; I see your note: > > > I have reviewed some log samples and all DO contain some kind of multi > line logs which are very uncomfortable to parse reliably in a log streamer. > > ... but I don't see any actual examples of those. Can you elaborate? > > -- > -- Christophe Pettus > x...@thebuild.com > > -- [image: XOE Solutions] <http://xoe.solutions/> DAVID ARNOLD Gerente General xoe.solutions dar@xoe.solutions +57 (315) 304 13 68 *Confidentiality Note: * This email may contain confidential and/or private information. If you received this email in error please delete and notify sender. *Environmental Consideration: * Please avoid printing this email on paper, unless really necessary.
