Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/1099#discussion_r203064655
--- 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 --
Should we explicitly say that when you use this type of topology so do NOT
create a sensor topology for any sensor included in the aggregate?
---
