Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/1099#discussion_r203095632
--- Diff: use-cases/parser_chaining/README.md ---
@@ -233,3 +233,10 @@ cat ~/data.log |
/usr/hdp/current/kafka-broker/bin/kafka-console-producer.sh --b
```
You should see indices created for the `cisco-5-304` and `cisco-6-302`
data with appropriate fields created for each type.
+
+# Aggregated Parsers with Parser Chaining
+Chained parsers can be run as aggregated parsers. These parsers continue
to use the sensor specific Kafka topics, and do not do internal routing to the
appropriate sensor.
+
--- End diff --
I think adding the follow on is a great idea. I wonder if we shouldn't
change the default install to aggregate the default sensors? I don't think
that will work though, because the comma separation in ambari is the list, and
you won't be able to do it.
My main concern is that the reviewers and committers of this pr are going
to be the only ones who can do it, and everyone in user land is going to be
lost. If this is going to be expert only ( until the UI comes ) and not
recommend, or a preview thing, maybe mark it as such.
---
