open-telemetry / open-telemetry/opentelemetry-java-contrib

`otel.resource.attributes` still not working in 1.52.0-alpha despite [#1416](https://github.com/open-telemetry/opentelemetry-java-contrib/issues/1416) fix

Open
#2,537 1 comment 0 reactions 2 assignees View on GitHub

@kenfinnigan is already working on this.

Since Jan 5, 2026.

bug component:maven-extension
Dominant language
Java
Stars
269
Forks
196
Avg merge
2d 7h
Merged PRs (30d)
38

Description

Component(s)

maven-extension

What happened?

Description

We are experiencing the same issue as #1416 where otel.resource.attributes and OTEL_RESOURCE_ATTRIBUTES are not applied to the Maven extension's resource, even in versions claimed to be fixed.

Steps to Reproduce

mvn -X clean verify -Dotel.resource.attributes="test.key=static,another.key=123"

Expected Result

Custom attributes from otel.resource.attributes should appear in the Maven service's resource.

Actual Result

Only default attributes appear

Working version

Tested 1.26.0-alpha - custom attributes do appear in resource.

Component version

v1.52.0

Log output

Maven debug log shows:

[INFO] OpenTelemetry: Initialize OpenTelemetrySdkService v1.52.0-alpha...
[DEBUG] OpenTelemetry: OTLP exporter endpoint is explicitly configured
[DEBUG] OpenTelemetry: OpenTelemetrySdkService initialized, resource:Resource{schemaUrl=null, attributes={service.name="maven", service.version="3.9.11", telemetry.distro.name="opentelemetry-maven-extension", telemetry.distro.version="1.52.0-alpha", telemetry.sdk.language="java", telemetry.sdk.name="opentelemetry", telemetry.sdk.version="1.56.0"}}

No test.key or another.key in the resource.

Additional context

No response

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

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.