You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Konstantine Karantasis (Jira)" <ji...@apache.org> on 2020/10/15 18:25:00 UTC
[jira] [Resolved] (KAFKA-10611) Merge log error to avoid double
error
[ https://issues.apache.org/jira/browse/KAFKA-10611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantine Karantasis resolved KAFKA-10611.
--------------------------------------------
Resolution: Fixed
> Merge log error to avoid double error
> -------------------------------------
>
> Key: KAFKA-10611
> URL: https://issues.apache.org/jira/browse/KAFKA-10611
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 2.6.0
> Reporter: Benoit MAGGI
> Priority: Trivial
> Fix For: 2.7.0
>
>
> When using an error tracking system, 2 error logs means 2 different alerts.
> It's best to group the logs and have one error with all information.
> For example when using with [Sentry|https://sentry.io/welcome/], this [double line|https://github.com/apache/kafka/blob/775f0d484b6fccc3d985a9d53d86d7a3710c0b22/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/WorkerTask.java#L187] of log.error will create 2 different Issues.
> One can merge the issues but it will be simpler to have a single error log line
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)