Hi Mark,
> In this scenario, should the nifi.cluster.load.balance.comms.timeout have
> caused the balancing operation to terminate (unsuccessful)?
I agree with that. Wasn't there any WARN log messages written?
Currently NiFi UI doesn't have capability to show load-balancing
related error on the
Hi Jon,
About reporting counter values, there is an existing JIRA for the
improvement idea to expose counters to Reporting task context. That
requires NiFi framework level improvements. I'd suggest taking a look
on it, and resuming discussion there if needed.
https://issues.apache.org/jira/browse/
Thanks for the input folks.
I had this impression that for actual processing of the data :
- we may have to put in place a custom processor which will have the
transformation framework logic in it.
- Or we can use ExcecuteProcess processor to trigger an external
process(which will be
Hello,
Did you add the windows-event-log nar to your MiNiFi distribution? This is
not a bundle that is automatically included. The log is creating a ghost
implementation as it cannot find a backing implementation for that
component coordinate. This is likely the best approach but you will need
Hi all...
I am trying to fetch remote windows server event logs in two ways
1.by installing minifi agent on the remote server and then created a minifi
config.yml with ConsumeWindowsEventLog processor and Remote process group
after that I have started minifi agent where ConsumeWindowsEventLog
pro
