Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Excessive INFO logging from ConfigurationUpdater after latest deployment

Abierto
#9,508 9 comentarios 1 reacción 1 asignado Ver en GitHub

@jpbempel ya está trabajando en esto.

Desde el 22/9/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Lenguaje dominante
Java
Estrellas
737
Forks
361
Merge medio
3 d 20 h
PR fusionados (30 d)
173

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DataDog/dd-trace-java

Todos los issues de DataDog/dd-trace-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.