Tracer log updated to use include exclude – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when the Elasticsearch tracer log configuration is updated to include or exclude certain actions. This is not necessarily an error, but more of an informational message indicating a change in the logging settings. To resolve this, you can either revert the changes if they were unintended or adjust the include/exclude settings to better suit your needs. You can also disable the tracer log if it’s not needed, which can help improve performance.

This guide will help you check for common problems that cause the log ” tracer log updated to use include: {}; exclude: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Index and Memory.

Log Context

Log “tracer log updated to use include: {}; exclude: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     Arrays.equals(newTracerLogExclude; TransportService.this.tracelLogExclude)) {
            TransportService.this.tracerLogInclude = newTracerLogInclude;
            TransportService.this.tracelLogExclude = newTracerLogExclude;
  "tracer log updated to use include: {}; exclude: {}"; newTracerLogInclude; newTracerLogExclude);

    // used for testing
    public void applySettings(Settings settings) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?