Collector v0.16.0 crashes when provided service.telemetry.metrics.address in YAML config

Abierto
  • ¿Algo no está bien?
#1,891 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
aws, go, yaml
Área
cloud, observability

Línea de trabajo

Comienza con collector/config.yaml, especialmente con service.telemetry.metrics.address, y compáralo con el esquema de configuración de Collector v0.16.0 y la documentación enlazada sobre la telemetría interna. Confirma si se debe eliminar o actualizar la configuración y, después, verifica que la extensión predeterminada de Collector se inicie correctamente con la configuración resultante.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Describe the bug
Collector v0.16.0 will fail to start as an extension, emitting the following error:

{
    "level": "warn",
    "ts": 1752100574.8841333,
    "logger": "lifecycle.manager",
    "msg": "Failed to start the extension",
    "error": "failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):\n\n'service.telemetry.metrics' decoding failed due to the following error(s):\n\n'' has invalid keys: address"
}

Steps to reproduce

I assume using the default config (i.e., providing no OPENTELEMETRY_COLLECTOR_CONFIG_URI) will elicit this behavior for any user of the Collector layer, since the default config still includes this property, but you can also use the collector-v0.16.0 branch of my repo to reproduce this issue.

The presence of

service:
  # ...
  telemetry:
    metrics:
      address: localhost:8888

is sufficient to crash the Collector extension layer.

Removing the entire telemetry portion will allow the Collector to successfully start; I'm not yet sure how this impacts the end user (e.g., if metrics are no longer received/exported).

What did you expect to see?

I expected to see the Collector extension layer start successfully and the Lambda execute successfully.

What did you see instead?

The extension crashes and the Lambda fails to execute.

What version of collector/language SDK version did you use?

This affects Collector v0.16.0.

What language layer did you use?

NodeJS v0.15.0

Additional context

Maybe this is expected behavior and the service.telemetry.metrics.address setting is deprecated or entirely unnecessary.

Update: I just found this in the documentation on the Collector's internal metrics:

Internal telemetry configuration changes

As of Collector v0.123.0, the service::telemetry::metrics::address setting is ignored. In earlier versions, it could be configured with:

service:
 telemetry:
   metrics:
     address: 0.0.0.0:8888
Lenguaje dominante
Go
Estrellas
433
Forks
249
Merge medio
1 d 12 h
PR fusionados (30 d)
39

Preparar el entorno

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 open-telemetry/opentelemetry-lambda

Todos los issues de open-telemetry/opentelemetry-lambda

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.