We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maven-extension
Setting the otel.resource.attributes doesn't work, contrary to documentation.
I tested a few versions - this was working in 1.27, and stopped working in 1.28 and does not work in latest.
Configure the opentelemetry-maven-extension (I'm exporting to Honeycomb, but I don't expect it to make a difference).
opentelemetry-maven-extension
Run:
mvn clean -Dotel.resource.attributes="key1=val1,key2=val2"
These attributes are exported to the otel collector.
These attributes are missing.
v1.28.0 - v.37.0
When building with 1.27 and -X, I get
-X
[DEBUG] ContextStorageClass=io.opentelemetry.context.ThreadLocalContextStorage, identity=375273627 classloader=ClassRealm[coreExtensi on>io.opentelemetry.contrib:opentelemetry-maven-extension:1.27.0-alpha, parent: ClassRealm[plexus.core, parent: null]] codeLocation=f ile:/Users/mwang/.m2/repository/io/opentelemetry/contrib/opentelemetry-maven-extension/1.27.0-alpha/opentelemetry-maven-extension-1.2 7.0-alpha.jar [DEBUG] OpenTelemetry: Initialize OpenTelemetrySdkService v1.27.0-alpha... [DEBUG] OpenTelemetry: OpenTelemetry SDK initialized with Configuration: otel.traces.exporter=otlp, otel.exporter.otlp.endpoint=https://api.honeycomb.io, otel.resource.attributes=key1=val1,key2=val2, Resource: {key1="val1", key2="val2", service.name="maven", service.version="3.9.8", telemetry.sdk.language="java", telemetry.sdk.name="opentelemetry", telemetry.sdk.version="1.27.0"} [DEBUG] OpenTelemetry: OpenTelemetry extension registered as execution listener. InitialExecutionListener: org.apache.maven.eventspy.internal.EventSpyExecutionListener@7e7fe6d [DEBUG] OpenTelemetry: afterSessionStart
When building with 1.28, I just see:
[DEBUG] OpenTelemetry: Initialize OpenTelemetrySdkService v1.28.0-alpha... [DEBUG] OpenTelemetry: OpenTelemetry SDK initialized [DEBUG] OpenTelemetry: OpenTelemetry extension registered as execution listener. InitialExecutionListener: org.apache.maven.eventspy.internal.EventSpyExecutionListener@4c447c09 [DEBUG] OpenTelemetry: afterSessionStart
No response
The text was updated successfully, but these errors were encountered:
Load OTelSDK config from environment variables and system properties. F…
ee61c7b
…ix open-telemetry#1416
See
Sorry, something went wrong.
Load OTel SDK config from environment variables and system properties. …
ecb469b
…Fix open-telemetry#1416
cyrille-leclerc
No branches or pull requests
Component(s)
maven-extension
What happened?
Description
Setting the otel.resource.attributes doesn't work, contrary to documentation.
I tested a few versions - this was working in 1.27, and stopped working in 1.28 and does not work in latest.
Steps to Reproduce
Configure the
opentelemetry-maven-extension
(I'm exporting to Honeycomb, but I don't expect it to make a difference).Run:
Expected Result
These attributes are exported to the otel collector.
Actual Result
These attributes are missing.
Component version
v1.28.0 - v.37.0
Log output
When building with 1.27 and
-X
, I getWhen building with 1.28, I just see:
Additional context
No response
The text was updated successfully, but these errors were encountered: