Sure, we have several data flow managers who are each responsible for a number of separate data flows, each of which lives in a separate processor group. When debugging, being able to see what's happening in your processor group (including full stack traces) is essential, but the noise from all the other processors is hugely distracting.
On Fri, 7 Sep 2018, 19:52 Joe Witt, <[email protected]> wrote: > James, > > One log per process group is not currently supported. Through things > like the message diagnostic context it might be pretty doable. > > That said, the logs aren't really meant to be the true historical > record of value. The data provenance entries are. Can you share more > about what you're trying to accomplish? > > Thanks > On Fri, Sep 7, 2018 at 2:47 PM James Srinivasan > <[email protected]> wrote: > > > > As we add more and more different processor groups doing separate > things, our nifi-app log is getting rather unmanageable. I'm probably > missing something obvious, but is one log per group possible? > > > > Thanks >
