Excessive INFO logging from ConfigurationUpdater after latest deployment

Open

#9,508 opened on Sep 10, 2025 9 comments 1 reaction 1 assignee View on GitHub

@jpbempel is already working on this.

Since Sep 22, 2025.

Assessment

This issue has not been assessed yet.

Description

comp: debugger type: bug report

Tracer Version(s)

1.53.0

Java Version(s)

21.0.8

JVM Vendor

Amazon Corretto

Bug Report

Title: Excessive INFO logging from ConfigurationUpdater after latest deployment

Description
After our latest deployment, we’ve observed an excessive amount of INFO logs coming from com.datadog.debugger.agent.ConfigurationUpdater. These logs appear to contain what should likely be DEBUG-level information.

Example logs:

[dd.trace 2025-09-10 13:40:36:595 +0000] [dd-task-scheduler] INFO com.datadog.debugger.agent.ConfigurationUpdater - Re-transforming class: ar.com.glamit.spring.configurations.config.ConfigurationCreatorConfig

[dd.trace 2025-09-10 13:40:36:730 +0000] [dd-task-scheduler] INFO com.datadog.debugger.agent.ConfigurationUpdater - Applying new probe configuration, changes: ConfigurationComparer{addedDefinitions=1, removedDefinitions=0, filteredListChanged=false, changedBlockedTypes=0}

Impact
These INFO logs are displayed as ERROR in the Datadog Web UI, creating noise and confusion for users monitoring logs.

Suspected cause
Upon reviewing the agent code, the logging level seems incorrectly set to INFO instead of DEBUG:

private void retransformClasses(List<Class<?>> classesToBeTransformed) {
  for (Class<?> clazz : classesToBeTransformed) {
    try {
      LOGGER.info("Re-transforming class: {}", clazz.getTypeName());
      instrumentation.retransformClasses(clazz);
    } catch (Exception ex) {
      ExceptionHelper.logException(LOGGER, ex, "Re-transform error:");
    } catch (Throwable ex) {
      ExceptionHelper.logException(LOGGER, ex, "Re-transform throwable:");
    }
  }
}

Expected behavior
These messages should likely be logged at the DEBUG level (or possibly TRACE), as they represent internal instrumentation details rather than actionable operational events.

Expected Behavior

Please confirm whether this logging level is intentional, and if not, consider adjusting it to reduce noise in production environments.

Reproduction Code

No response

Dominant language: Java
Stars: 737
Forks: 361
Avg merge: 3d 20h
Merged PRs (30d): 173

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Compatibility certification request for FJ-EAP 2.1.0 for Jakarta EE Platform 11 Open

certification

Difficulty 1/5 Under an hour Newbie friendliness 80/100

jakartaee/platform#1359 · Opened Sep 24, 2026
Python guide test runner copies stale Micronaut Test Resources state Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

micronaut-projects/micronaut-guides#1856 · Opened Sep 23, 2026
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Open

bug ecr

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

floci-io/floci#4264 · Opened Sep 23, 2026
Drop point numbers from GitHub milestones Open

Needs: Triage Type: Feature request

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

AntennaPod/AntennaPod#8794 · Opened Sep 23, 2026
[aw] Issue Classification Agent timed out Open

agentic-workflows

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

github/copilot-sdk#2760 · Opened Sep 23, 2026

More Java issues