open-telemetry / open-telemetry/opentelemetry-java

Make declarative config YAML parsing and object mapping requirements pluggable via SPI

Open
#8,820 1 comment 0 reactions 1 assignee View on GitHub

@jack-berg is already working on this.

Since Sep 14, 2026.

Feature Request
Dominant language
Java
Stars
2.5k
Forks
1k
Avg merge
3d 17h
Merged PRs (30d)
58

Description

For declarative config is affected. I think a good way to do this is to make the task of taking parsing YAML and/or converting to pojo pluggable via SPI.

Roughly, the process looks like:

Object parsedYaml = org.snakeyaml.engine.v2.api.Load.loadFromInputStream(InputStream);
OpenTelemetryConfigurationModel model = com.fasterxml.jackson.databind.ObjectMapper.convertValue(parsedYaml, OpenTelemetryConfigurationModel.class);
OpenTelemetrySdk openTelemetrySdk = create(model);

So things we need to be pluggable:

  • Parsing YAML InputStream to Object
  • Converting Object to POJO

The serialization stuff in the unsupported OTLP json path adds more complexity since the API surface area of JsonSerializer is large.

Originally posted by @jack-berg in #8533

Contributor guide

Open the contributing guide

First steps

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

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.