Ah, for (9), I used system-diagnostics. (I had not spelled it correctly when trying it before.)
On Fri, Jul 8, 2016 at 3:35 PM, Russell Bateman < [email protected]> wrote: > I'm trying to figure out how to use the ReST (nifi-api) interface to > accomplish a number of things. First, I've played successfully with it > doing simple things like getting configuration, a list of existing > processors, and the like. I've even discovered that in > controller/history/processors/{processorId} I can use the processor name > for {processorId} instead of an intangible or impossible number. > > What puzzles me is that I need a {process-group-id} to do so many things. > I'm not using a process group, my flow is very simple for now. Maybe, think > I, I have one process group and I just need its id, but how do I get that? > I see no list API for it. > > The long list of things I'm hoping to do down the road from a UI is to be > able to see things like: > > 1. How many times a processor processed anything? > 2. How many flowfiles were processed? > 3. How many flowfiles were produced? > 4. Can I get this information per processor? > 5. How can I tell different instances of the same processor apart? > 6. Why can't I see the name I gave a processor in configuration? (For > example, I named an instance of GetFile to "Get PDF files from test > fodder". > 7. How can I get a list of items on the NiFi canvas like processors > and relationships. > 8. How many times processors or a processor failed? > 9. What is the profile of resource usage, like memory in use? > 10. What is the profile of processor latency? > - flowfiles backed up awaiting processing > - flowfiles in other states (?) > > Any nudge on any of this would be very welcome. NiFi is new enough that > there's precious few samples of people using the ReST interface. > > Thanks >
