Ryan, I've considered implementing something like this before but just never had the cycles. I do think it's a good idea, though. The approach that I would take is to write a Reporting Task, though. It would not be any change to the framework. Rather, the reporting task would just run, say every 5 minutes or so and if it finds any processors that are stopped, keep track of when it was stopped. After some amount of time, if it's still stopped, send an e-mail.
I think this is very doable. I don't know if you're interested in getting more involved with NiFi or not, but I think it would be a great place to dig in, if you are interested. Thanks -Mark > On Jan 19, 2016, at 6:02 PM, Ryan H <rhendrickson.w...@gmail.com> wrote: > > How about this.. Add another "stop" state that includes a notification to a > distro every 5 minutes a processor is stopped. That way if you stop a > production processor, leave for the day, and forget to turn it back on, > it's at least spamming a distro to remind you or your group to click > "start" again. > > Ryan
