@Iyappan Gopalakrishnan Adding new users to a secured NiFI 0.x / HDF 1.x version of NiFi can be done directly via the NIFi UI. I am assuming you have already secured your NiFi and manually added the initial admin to the authorized-users.xml file. Adding new users is pretty easy. Simply have the new user attempt to access the https web address for your nifi 0.7 install. After authenticating successfully (Done via client certs, ldap, etc), they will see a screen telling them they are not authorized for access and giving them the opportunity to request access. Once they request access, the "Admin" user who does have access to the UI will need need to go into the users UI by clicking on the below Icon which can be found in the upper right corner of the NiFi UI: From within that UI you will see all existing users and any pending authorization users. Simply click on the pencil icon to the right of any pending users to authorize them for 1 or more of the available user roles (Administrator, Dataflow Manger, Read Only, or Provenance). The administration-guide included with your install can give you more details on each of the roles and what privileges each grants to the users. Thanks, Matt ... View more

Looks like the Twitter API puts hash tags into the following JSON: "entities": { "hashtags":[], "urls":[], "user_mentions":[] } You could use EvaluteJsonPath to extract the value of the hashtags into FlowFile attributes, and then use RouteOnAttribute to route the ones matching your tag to a PutFile processor. This blog shows an example of extracting values from the Twitter JSON and making routing decisions: https://blogs.apache.org/nifi/entry/indexing_tweets_with_nifi_and ... View more

There are a few things you can do here if i am understanding correctly what you are trying to accomplish. 1. The logback.xml can be modified so specific processor component logs could be redirected to a specific new log file. You can specify where that new log is written. You could also specify the specific log level of those components (WARN level would get you just WARN and ERROR messages). 2. In your dataflow you could use the TailFile processor to monitor that new log and route any generated FlowFiles to a putEmail processor to send them to your Admin. In addition to email you can route those FlowFiles to a processor of your choice to put a copy to a specific location as well either locally or remotely. Thanks, Matt ... View more