Skip to content

Commit

Permalink
fix: removed stacktrace from periodic error message
Browse files Browse the repository at this point in the history
fixes AM-3909 - In preparation for introducing Degraded Mode, we noticed a flood of the same messages with useless stack traces. By default, this keeps them on one line. To revert this, the log level can be set to DEBUG.
  • Loading branch information
lgw-gravitee committed Sep 24, 2024
1 parent 5480516 commit 7633706
Showing 1 changed file with 15 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,11 @@ private void registerClusterListener() {
.createOrUpdate(convert(message.content()))
.ignoreElement()
.onErrorResumeNext(throwable -> {
log.error("Unable to process node infos message", throwable);
if (log.isDebugEnabled()) {
log.error("Unable to process node infos message", throwable);
} else {
log.error("Unable to process node infos message, ex={}", throwable.toString());
}
return Completable.complete();
})
.subscribe();
Expand All @@ -96,7 +100,11 @@ private void registerClusterListener() {
.createOrUpdate(convert(message.content()))
.ignoreElement()
.onErrorResumeNext(throwable -> {
log.error("Unable to process health check message", throwable);
if (log.isDebugEnabled()) {
log.error("Unable to process health check message", throwable);
} else {
log.error("Unable to process health check message, ex={}", throwable.toString());
}
return Completable.complete();
})
.subscribe();
Expand All @@ -112,7 +120,11 @@ private void registerClusterListener() {
.createOrUpdate(convert(message.content()))
.ignoreElement()
.onErrorResumeNext(throwable -> {
log.error("Unable to process monitor message", throwable);
if (log.isDebugEnabled()) {
log.error("Unable to process monitor message", throwable);
} else {
log.error("Unable to process monitor message, ex={}", throwable.toString());
}
return Completable.complete();
})
.subscribe();
Expand Down

0 comments on commit 7633706

Please sign in to comment.