It should be in nifi-app.log... in the code it does: context.getBulletinRepository().addBulletin(bulletin); logger.warn(message); The logger is a standard SLF4J logger which ends up being logback controlled by the logback.xml in the conf directory: Logger logger = LoggerFactory.getLogger(MonitorDiskUsage.class); ... View more

This example uses site-to-site to send logs from one instance to another using a push model: https://github.com/bbende/nifi-streaming-examples The first instance has a Remote Process Group pointing to the URL of the second instance. The second instance has an Input Port to receive logs, which the Remote Process Group from the first instance is connected to. You also need to enable nifi.remote.input.socket.port and nifi.remote.input.secure on the node where the an incoming connection will be made. In this example that is the node with the Input Port which will receive an incoming connection from the Remote Process Group on the first node. ... View more

In EvaluateJsonPath, you can choose "flowfile-attribute" as the Destination, then the original JSON will still be in the flow file content, and any extracted JSON elements will be in the flowfile's attributes. That can go into RouteOnAttribute for "eventname". Then you can use ReplaceText (or ExecuteScript if you prefer) to create a CQL statement using Expression Language to insert the values from your attributes, or to wrap the entire JSON object in a CQL statement. I have a template that uses ReplaceText to put an entire JSON object into a "INSERT INTO myTable JSON" CQL statement, it is available as a Gist (here). It doesn't have a PutCassandraQL processor at the end, instead its a LogAttribute processor so you can see if the CQL looks right for what you're trying to do. ... View more