Thanks Kei, I got most of the information. I have one question about the history run.
Lets say I have a flow of 10 processors, I would like to see the history of this flow run. will Data provenance show us combine flow or individual processor levels? On Wed, Aug 28, 2019 at 11:14 AM Kei Schaff <[email protected]> wrote: > *Version control*: Keeping the development modular through the use of > process groups helps. We use NiFi Registries to track changes in both > development and production environments. We also separately create > templates > of process groups that we version control with git. Although, the templates > are XML files, viewing differences and doing merges are usually too > difficult to be practicable. > > *Prod Migration*: When promoting a process group from development to > production we normally import the git-managed templates of process groups. > It is also possible to get the process groups directly from the development > environment's NiFi registry. In either case, there are always manual steps > to take, such as setting sensitive parameters and configuring controllers. > > *Job Monitoring*: We normally only monitor failures by having the sent (via > HttpInvoke) to an external alerting system. We have also used the NiFi REST > API to create data points that are sent to AWS CloudWatch to see the > historical data volumes of various process groups (usually representing > distinct data sets or providers). We have integrated NiFi with Cloudera > (before the Horton Works merger) to get server status. > > *External Schedulers*: There are so many ways to integrate with external > schedulers. In addition to a scheduler pushing an event via a NiFi REST API > call, NiFi can listen for external events through processors that read a > (local or remote) file system, monitor queues, perform REST calls, etc. > > *History Run Log*: NiFi's provenance is likely what you are looking for > here. Also, any part of a NiFi flow can be instrumented to log information > externally, as well. > > Although, your environment is likely different from ours. I hope these > ideas > help. > > On Wed, Aug 28, 2019 at 11:16 AM KhajaAsmath Mohammed < > [email protected]> wrote: > >> Hi, >> >> I have few questions on nifi as we are implementing it in our production >> environment. >> >> >> - How to perform version control among multiple developers >> - What’s the strategy to do QA/Prod migration >> - Job monitoring in NiFi >> - Can the NiFi flows be integrated with external schedulers ( maybe >> it needs to be through API?) >> - Is there a history run log, for example, is it possible to check >> the status or error message for the run 3 days ago? >> >> >> Thanks, >> Mohd >> >
