[
https://issues.apache.org/jira/browse/METRON-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878574#comment-15878574
]
ASF GitHub Bot commented on METRON-694:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/453
Thanks @merrimanr . Error message has tons of useful fields. I like it.
I think your option 2 above ('source.type=error' with a separate field for
original source type) would be very useful. I am just not sure if we can
assume we always know the original source type.
If a message errored early in parsing then maybe we don't know the
`source.type`? Or can we always assume the `source.type` based on the Kafka
topic that we got the message from?
I think your option 1 is a good fall-back, if we cannot always assume we
know the `source.type`.
> 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)
