Merge branch 'main' into camel-metadata

Author: trask

.github/workflows/release.yml

@@ -21,6 +21,8 @@ jobs:
   release:
     permissions:
       contents: write # for creating the release
+      id-token: write # for signing artifacts with Sigstore
+      attestations: write # for uploading attestations
     runs-on: ubuntu-latest
     needs:
       - common
@@ -170,13 +172,22 @@ jobs:
           .github/scripts/generate-release-contributors.sh v$PRIOR_VERSION >> /tmp/release-notes.txt
           fi
 
+      - name: Simplify paths for attaching
+        run: |
+          cp javaagent/build/libs/opentelemetry-javaagent-${VERSION}.jar opentelemetry-javaagent.jar
+          cp javaagent/build/libs/opentelemetry-javaagent-${VERSION}.jar.asc opentelemetry-javaagent.jar.asc
+
+      - uses: actions/attest-build-provenance@977bb373ede98d70efdf65b84cb5f73e068dcc2a # v3.0.0
+        with:
+          subject-path: |
+            opentelemetry-javaagent.jar
+            opentelemetry-java-instrumentation-SBOM.zip
+
       - id: create-github-release
         name: Create GitHub release
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
-          cp javaagent/build/libs/opentelemetry-javaagent-${VERSION}.jar opentelemetry-javaagent.jar
-          cp javaagent/build/libs/opentelemetry-javaagent-${VERSION}.jar.asc opentelemetry-javaagent.jar.asc
           gh release create --target $GITHUB_REF_NAME \
                             --title "Version $VERSION" \
                             --notes-file /tmp/release-notes.txt \

CHANGELOG.md

@@ -2,6 +2,103 @@
 
 ## Unreleased
 
+## ⚠️ Breaking Changes
+
+- Hadoop JMX metrics have been renamed to align with semantic conventions.
+  If you are using Hadoop JMX metrics, you will need to update your dashboards and alerts.
+  ([#14411](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14411))
+- Lettuce 5.1 instrumentation now aligns with other instrumentations and no longer sets the
+  span status description.
+  ([#14886](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14886))
+
+## 🚫 Deprecations
+
+- The following Logback appender configuration properties have been renamed for clarity.
+  The old property names have been deprecated and will be removed in a future release:
+  - Java agent: `otel.instrumentation.logback-appender.experimental.capture-logstash-attributes` →
+    `otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes`
+  - Spring Boot starter`otel.instrumentation.logback-appender.experimental.capture-logstash-markers` →
+    `otel.instrumentation.logback-appender.experimental.capture-logstash-marker-attributes`
+  - Logback appender configuration property: `captureLogstashAttributes` → `captureLogstashMarkerAttributes`
+  - Logback appender API: `setCaptureLogstashAttributes()` → `setCaptureLogstashMarkerAttributes()`
+  ([#14959](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14959))
+
+### 🌟 New javaagent instrumentation
+
+- Add Helidon instrumentation
+  ([#13776](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13776))
+- Add NATS instrumentation
+  ([#13999](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13999))
+- OpenSearch Transport v3.0 Implementation
+  ([#14823](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14823))
+- Add Kafka Connect API instrumentation
+  ([#14478](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14478))
+
+### 🌟 New library instrumentation
+
+- Add Helidon Instrumentation
+  ([#13776](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13776))
+- Add NATS instrumentation
+  ([#13999](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13999))
+- [Failsafe](https://failsafe.dev/) 3.0 instrumentation introduced
+  ([#14057](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14057))
+
+### 📈 Enhancements
+
+- Add experimental sqlcommenter support for JDBC and R2DBC
+  ([#13714](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13714))
+- Align Hadoop JMX metrics with semantic conventions
+  ([#14411](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14411))
+- Introduce experimental API for operation attributes to be passed only to OperationListeners
+  ([#14590](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14590))
+- Add span logging support for declarative configuration
+  ([#14591](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14591))
+- Add span logging support for Spring Boot starter
+  ([#14594](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14594))
+- Support capturing event names in logback, log4j, and jboss-logmanager appenders
+  ([#14649](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14649))
+- Include contrib sampler in java agent, e.g. for filtering health check endpoints
+  ([#14677](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14677))
+- Collect RPC metrics in Apache Dubbo instrumentation
+  ([#14690](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14690))
+- Add experimental option to disable noisy `redis.encode` span events in Lettuce instrumentation
+  ([#14750](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14750))
+- Support ListIterator in Kafka consumer instrumentation for Spark Structured Streaming
+  ([#14757](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14757))
+- Exclude wrapper classes in JDBC instrumentation
+  ([#14760](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14760))
+- Support JDBC URL parsing for OceanBase, PolarDB, and Lindorm databases
+  ([#14790](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14790))
+- Support context propagation in Guava AsyncEventBus
+  ([#14791](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14791))
+- Make `db.statement` attribute available during sampling in Lettuce instrumentation
+  ([#14856](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14856))
+- Add `code.namespace` and `code.function` attributes to Vaadin controller spans
+  ([#14882](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14882))
+- Add `code.namespace` and `code.function` attributes to Grails controller spans
+  ([#14885](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14885))
+- Support Hibernate 7.2.0.CR1
+  ([#14921](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14921))
+- Support capturing Logstash StructuredArguments as log record attributes
+  ([#14959](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14959))
+- Add gRPC request/response size metrics
+  ([#14342](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14342))
+
+### 🛠️ Bug fixes
+
+- Fix datasource instrumentation to support connection pools like Druid
+  ([#14602](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14602))
+- Fix Java HTTP client instrumentation to properly propagate request cancellation
+  ([#14747](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14747))
+- Fix Reactor Netty HTTP client instrumentation to handle IllegalStateException
+  ([#14778](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14778))
+- Fix executor context propagation when a stateless lambda instance is passed multiple times
+  ([#14841](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14841))
+- Remove span status description from Lettuce 5.1 instrumentation
+  ([#14886](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/14886))
+- Fix Spring Boot autoconfiguration ordering for micrometer bridge
+  ([#15011](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/15011))
+
 ## Version 2.20.1 (2025-09-22)
 
 ### 🛠️ Bug fixes

RELEASING.md

@@ -65,8 +65,10 @@ and deadlocks.
 - Run the [Release workflow](https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/workflows/release.yml).
   - Press the "Run workflow" button, then select the release branch from the dropdown list,
     e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
-  - This workflow will publish the artifacts to maven central and will publish a GitHub release
-    with release notes based on the change log and with the javaagent jar attached.
+  - This workflow will:
+    - Publish the artifacts to Maven Central
+    - Generate [GitHub Artifact Attestations](https://docs.github.com/en/actions/security-for-github-actions/using-artifact-attestations) for the Java agent jar and SBOM bundle
+    - Publish a GitHub release with release notes, Java agent jar, and SBOM bundle
   - Review and merge the pull request that it creates for updating the apidiff baseline version
     to the newly released version (note that this pull request won't be made until after the release
     is available in maven central).

docs/instrumentation-list.yaml

@@ -2049,6 +2049,9 @@ libraries:
     description: This instrumentation enables context propagation for the Azure Core
       library, it does not emit any telemetry on its own.
     library_link: https://learn.microsoft.com/en-us/java/api/overview/azure/core-readme?view=azure-java-stable
+    features:
+    - CONTEXT_PROPAGATION
+    - AUTO_INSTRUMENTATION_SHIM
     source_path: instrumentation/azure-core/azure-core-1.14
     scope:
       name: io.opentelemetry.azure-core-1.14
@@ -2059,6 +2062,9 @@ libraries:
     description: This instrumentation enables context propagation for the Azure Core
       library, it does not emit any telemetry on its own.
     library_link: https://learn.microsoft.com/en-us/java/api/overview/azure/core-readme?view=azure-java-stable
+    features:
+    - CONTEXT_PROPAGATION
+    - AUTO_INSTRUMENTATION_SHIM
     source_path: instrumentation/azure-core/azure-core-1.19
     scope:
       name: io.opentelemetry.azure-core-1.19
@@ -2069,6 +2075,9 @@ libraries:
     description: This instrumentation enables context propagation for the Azure Core
       library, it does not emit any telemetry on its own.
     library_link: https://learn.microsoft.com/en-us/java/api/overview/azure/core-readme?view=azure-java-stable
+    features:
+    - CONTEXT_PROPAGATION
+    - AUTO_INSTRUMENTATION_SHIM
     source_path: instrumentation/azure-core/azure-core-1.36
     scope:
       name: io.opentelemetry.azure-core-1.36
@@ -2079,6 +2088,8 @@ libraries:
   - name: c3p0-0.9
     description: The c3p0 instrumentation provides connection pool metrics for c3p0
       data sources.
+    semantic_conventions:
+    - DATABASE_POOL_METRICS
     library_link: https://github.com/swaldman/c3p0
     source_path: instrumentation/c3p0-0.9
     scope:

instrumentation/azure-core/azure-core-1.14/metadata.yaml

@@ -1,2 +1,5 @@
 description: This instrumentation enables context propagation for the Azure Core library, it does not emit any telemetry on its own.
+features:
+  - CONTEXT_PROPAGATION
+  - AUTO_INSTRUMENTATION_SHIM
 library_link: https://learn.microsoft.com/en-us/java/api/overview/azure/core-readme?view=azure-java-stable

instrumentation/azure-core/azure-core-1.19/metadata.yaml

@@ -1,2 +1,5 @@
 description: This instrumentation enables context propagation for the Azure Core library, it does not emit any telemetry on its own.
+features:
+  - CONTEXT_PROPAGATION
+  - AUTO_INSTRUMENTATION_SHIM
 library_link: https://learn.microsoft.com/en-us/java/api/overview/azure/core-readme?view=azure-java-stable

instrumentation/azure-core/azure-core-1.36/metadata.yaml

@@ -1,2 +1,5 @@
 description: This instrumentation enables context propagation for the Azure Core library, it does not emit any telemetry on its own.
+features:
+  - CONTEXT_PROPAGATION
+  - AUTO_INSTRUMENTATION_SHIM
 library_link: https://learn.microsoft.com/en-us/java/api/overview/azure/core-readme?view=azure-java-stable

instrumentation/c3p0-0.9/metadata.yaml

@@ -1,2 +1,4 @@
 description: The c3p0 instrumentation provides connection pool metrics for c3p0 data sources.
+semantic_conventions:
+  - DATABASE_POOL_METRICS
 library_link: https://github.com/swaldman/c3p0

instrumentation/jmx-metrics/library/jetty.md

@@ -10,31 +10,31 @@ The metrics captured and their respective attributes depend on the Jetty version
 
 Those metrics require the following Jetty modules to be enabled : `jmx`, `http`, `statistics`, `sessions` and at least one of `ee8-deploy`, `ee9-deploy` or `ee10-deploy`.
 
-| Metric Name             | Type          | Attributes    | Description                               |
-|-------------------------|---------------|---------------|-------------------------------------------|
-| jetty.thread.count      | UpDownCounter |               | The current number of threads             |
-| jetty.thread.limit      | UpDownCounter |               | The maximum number of threads in the pool |
-| jetty.thread.busy.count | UpDownCounter |               | The current number of busy threads        |
-| jetty.thread.idle.count | UpDownCounter |               | The current number of idle threads        |
-| jetty.thread.queue.size | UpDownCounter |               | The current job queue size                |
-| jetty.io.select.count   | Counter       |               | The number of select calls                |
-| jetty.session.count     | UpDownCounter | jetty.context | Current number of active sessions         |
+| Metric Name             | Type          | Unit        | Attributes    | Description                               |
+|-------------------------|---------------|-------------|---------------|-------------------------------------------|
+| jetty.thread.count      | UpDownCounter | {thread}    |               | The current number of threads             |
+| jetty.thread.limit      | UpDownCounter | {thread}    |               | The maximum number of threads in the pool |
+| jetty.thread.busy.count | UpDownCounter | {thread}    |               | The current number of busy threads        |
+| jetty.thread.idle.count | UpDownCounter | {thread}    |               | The current number of idle threads        |
+| jetty.thread.queue.size | UpDownCounter | {thread}    |               | The current job queue size                |
+| jetty.io.select.count   | Counter       | {operation} |               | The number of select calls                |
+| jetty.session.count     | UpDownCounter | {session}   | jetty.context | Current number of active sessions         |
 
 - `jetty.context` corresponds to the deployed application subfolder in `webapps` folder.
 
 ## Jetty 9 to 11
 
 Those metrics require the following Jetty modules to be enabled : `jmx`, `http` and `stats`.
 
-| Metric Name                 | Type          | Attributes    | Description                               |
-|-----------------------------|---------------|---------------|-------------------------------------------|
-| jetty.thread.count          | UpDownCounter |               | The current number of threads             |
-| jetty.thread.limit          | UpDownCounter |               | The maximum number of threads in the pool |
-| jetty.thread.busy.count     | UpDownCounter |               | The current number of busy threads        |
-| jetty.thread.idle.count     | UpDownCounter |               | The current number of idle threads        |
-| jetty.thread.queue.size     | UpDownCounter |               | The current job queue size                |
-| jetty.io.select.count       | Counter       |               | The number of select calls                |
-| jetty.session.created.count | Counter       | jetty.context | The total number of created sessions      |
-| jetty.session.duration.sum  | Counter       | jetty.context | The cumulated session duration            |
+| Metric Name                 | Type          | Unit        | Attributes    | Description                               |
+|-----------------------------|---------------|-------------|---------------|-------------------------------------------|
+| jetty.thread.count          | UpDownCounter | {thread}    |               | The current number of threads             |
+| jetty.thread.limit          | UpDownCounter | {thread}    |               | The maximum number of threads in the pool |
+| jetty.thread.busy.count     | UpDownCounter | {thread}    |               | The current number of busy threads        |
+| jetty.thread.idle.count     | UpDownCounter | {thread}    |               | The current number of idle threads        |
+| jetty.thread.queue.size     | UpDownCounter | {thread}    |               | The current job queue size                |
+| jetty.io.select.count       | Counter       | {operation} |               | The number of select calls                |
+| jetty.session.created.count | Counter       | {session}   | jetty.context | The total number of created sessions      |
+| jetty.session.duration.sum  | Counter       | {session}   | jetty.context | The cumulated session duration            |
 
 - `jetty.context` corresponds to the deployed application subfolder in `webapps` folder.