Github user merrimanr commented on the issue: https://github.com/apache/incubator-metron/pull/453 So the consensus is to use a single indexing topology for both error and normal messages by default. I will remove the scripts and configuration (flux and properties) files and remove the error indexing topology from the MPack. If a user wants to use a separate error indexing topology it will be their responsibility to change error topic setting and start a separate indexing topology. Does this sound ok to everyone? A couple questions are still unanswered. How granular should the error topic setting be? I will assume global config is acceptable unless I hear otherwise. Also, as @cestella alluded to earlier, what should the structure of the source.type field be? I see these as possibilities: 1. source.type is 'error' with sensor name and error type in separate fields (1 index config) 2. source.type is error type with sensor name in separate field (index config per error type) 3. source.type is sensor name + '_error' (additional error index config per sensor) If no one has any strong opinions I will stick with option 1.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---