I think the first thing would be to expose as much data about the record sets as possible in the flow. The second would be to consider some UI work to make things a little flashier in the way that attracted his eye to Streamsets.
I don't think we need the live monitoring because with s2s you can easily integrate ELK and get something as flashy as Streamsets, but we need something that can be used to help ELK visualize what record sets were processed. On Tue, May 22, 2018 at 12:37 AM Joe Witt <[email protected]> wrote: > Mike, > > What specifically do you have in mind? There are a lot of good/useful > things we can do of course. For instance we can make records a first > class part of the nifi-api and then provide live monitoring over them. > We have tons of good data in that regard. But, we must also be > mindful of the need to make progress on the extension registry as > well. > > Thanks > > On Mon, May 21, 2018 at 4:17 PM, Mike Thomsen <[email protected]> > wrote: > > https://statsbot.co/blog/open-source-etl/ > > > > Someone on my team shared that. Overall, it's a very fair take. I think > it > > has some direct action items, particularly on the UX side that could be > > considered for 1.8 to close some gaps. > > > > (Not trying to start a flame war here, as once again I think it's a fair > > article) > > > > Mike >
