Hi,
I'm currently investigating the suitability of using an Embedded Agent with a
file based channel which will be used to write to another agent with a file
based channel, and then ultimately into a hdfs sequence file. I've done some
early testing in a local environment (with a VM acting as a
In our test environment, we have a few flume 1.4 instances running. We are
seeing the following when using the Http Json Monitoring:
1) Despite having multiple, distinct source-channel-sink combos, the
counters for take attempt counts on all of our channels are set to the same
exact non-zero numb