[
https://issues.apache.org/jira/browse/METRON-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876064#comment-15876064
]
ASF GitHub Bot commented on METRON-694:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/453
I think a configurable error topic is a reasonable request. The
requirements need a little clarification though.
How granular should this configuration property be? Should it be kept in
the global config? Do we want to expose this property per topology? In that
case it would need to be added to parser configs and flux properties. Do we
want it to be per sensor? In that case it would be added to sensor, enrichment
and indexing configs.
Should this topology be on by default or not? If it's off by default then
there is no ansible work to be done other than deploying configurations.
@cestella, in the case that it's off by default, what would you consider
functioning in vagrant to be?
> Index Errors from Topologies
> ----------------------------
>
> Key: METRON-694
> URL: https://issues.apache.org/jira/browse/METRON-694
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
>
> Need to make sure (and review) that all the bolts write into the error queue.
> Errors should then be consumed from the error queue and indexed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
