Tracer log updated to use include: ; exclude: – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content