[
https://issues.apache.org/jira/browse/EAGLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650155#comment-15650155
]
ASF GitHub Bot commented on EAGLE-758:
--------------------------------------
Github user garrettlish commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/631#discussion_r87147672
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/spout/SpoutOutputCollectorWrapper.java
---
@@ -103,7 +103,7 @@ public SpoutOutputCollectorWrapper(CorrelationSpout
spout,
*/
List<Object> convertedTuple = converter.convert(tuple);
if (convertedTuple == null) {
- LOG.warn("source data {} can't be converted to a stream,
ignore this message", tuple);
+ LOG.debug("source data {} can't be converted to a stream,
ignore this message", tuple);
--- End diff --
If u are log the message without manipulating, it is unnecessary to add
isDebugEnabled check since debug method will do the same thing.
> Add tuple log for spout & alert bolt
> ------------------------------------
>
> Key: EAGLE-758
> URL: https://issues.apache.org/jira/browse/EAGLE-758
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Garrett Li
> Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Without tuple log for spout & alert bolt, it is hard to troubleshoot event
> missing issue, we don't know whether the spout/alert process issue or no
> event come.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)