dependabot[bot] opened a new pull request, #20638:
URL: https://github.com/apache/druid/pull/20638

   Bumps 
[io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha](https://github.com/open-telemetry/opentelemetry-java-instrumentation)
 from 2.31.1-alpha to 2.32.0-alpha.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases";>io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha's
 releases</a>.</em></p>
   <blockquote>
   <h2>Version 2.31.1</h2>
   <p>This release targets the OpenTelemetry SDK 1.65.0.</p>
   <p>Note that many artifacts have the <code>-alpha</code> suffix attached to 
their version number, reflecting that they will continue to have breaking 
changes. Please see <a 
href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/VERSIONING.md#opentelemetry-java-instrumentation-versioning";>VERSIONING.md</a>
 for more details.</p>
   <h3>🛠️ Bug fixes</h3>
   <ul>
   <li>Restore stable semantic convention APIs to the compile classpaths of the 
Spring Boot autoconfigure and starter artifacts. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19754";>#19754</a>)</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md";>io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha's
 changelog</a>.</em></p>
   <blockquote>
   <h1>Changelog</h1>
   <h2>Unreleased</h2>
   <h3>⚠️ Breaking changes</h3>
   <ul>
   <li>
   <p>The Java agent no longer captures thread details by default. Set
   <code>otel.javaagent.add-thread-details=true</code> to capture 
<code>thread.id</code> and <code>thread.name</code> on spans.</p>
   </li>
   <li>
   <p>GenAI message events from AWS Bedrock Runtime and OpenAI leave the body 
unset when no fields
   remain, instead of emitting an empty object.</p>
   </li>
   <li>
   <p>Process command resource attributes are now disabled by default. Set
   
<code>otel.instrumentation.resources.experimental.process-command-attributes.enabled=true</code>
 to capture
   <code>process.command_args</code> and <code>process.command_line</code>.</p>
   </li>
   <li>
   <p>Declarative Java agent instrumentation selectors no longer accept 
dotted-version compatibility
   spellings. In <code>distribution.javaagent.instrumentation.enabled</code> 
and <code>.disabled</code>, replace
   selectors such as <code>reactor_3.1</code> with <code>reactor_3_1</code>.</p>
   </li>
   <li>
   <p>Java agent telemetry now uses the following instrumentation scopes. 
Update views, dashboards
   and filters matching the previous names:</p>
   <table>
   <thead>
   <tr>
   <th>Previous scope</th>
   <th>Current scope</th>
   </tr>
   </thead>
   <tbody>
   <tr>
   <td><code>io.opentelemetry.jaxrs-1.0</code></td>
   <td><code>io.opentelemetry.jaxrs-1.0-annotations</code></td>
   </tr>
   <tr>
   <td><code>io.opentelemetry.jaxws-cxf-3.0</code></td>
   <td><code>io.opentelemetry.jaxws-2.0-cxf-3.0</code></td>
   </tr>
   <tr>
   <td><code>io.opentelemetry.jaxws-metro-2.2</code></td>
   <td><code>io.opentelemetry.jaxws-2.0-metro-2.2</code></td>
   </tr>
   <tr>
   <td><code>io.opentelemetry.mongo-3.7</code></td>
   <td><code>io.opentelemetry.mongo-3.1</code></td>
   </tr>
   <tr>
   <td><code>io.opentelemetry.ratpack-1.7</code></td>
   <td><code>io.opentelemetry.ratpack-1.4</code></td>
   </tr>
   <tr>
   <td><code>io.opentelemetry.tomcat-jdbc</code></td>
   <td><code>io.opentelemetry.tomcat-jdbc-8.5</code></td>
   </tr>
   </tbody>
   </table>
   </li>
   <li>
   <p>Couchbase Java SDK 3.1 and 3.2+ spans now use the agent-owned scope names 
instead of
   <code>com.couchbase.client.jvm</code>. SDK 3.1 uses 
<code>io.opentelemetry.couchbase-3.1</code>; SDK 3.2+ uses
   <code>io.opentelemetry.couchbase-3.2</code>.</p>
   </li>
   <li>
   <p>Java agent instrumentation selectors now always use the versioned 
component name first,
   followed by supported role, versionless and umbrella selectors. When several 
selectors are
   configured, the first matching selector determines enablement. For example,
   <code>otel.instrumentation.lettuce-5.0.enabled</code> takes precedence over
   <code>otel.instrumentation.lettuce.enabled</code>.</p>
   </li>
   <li>
   <p>Remove legacy Java agent selectors and implementation-only aliases from
   <code>otel.instrumentation.&lt;name&gt;.enabled</code>. Use the component 
selectors below. Where several
   implementations now share a component selector, there is no 
implementation-only replacement;
   the replacement controls the component as a whole.</p>
   <table>
   <thead>
   <tr>
   <th>Removed selectors</th>
   <th>Replacement selectors</th>
   </tr>
   </thead>
   <tbody>
   <tr>
   <td><code>akka-actor-2.3-core</code>, <code>akka-actor-fork-join</code>, 
<code>akka-actor-fork-join-2.5</code>, <code>akka-actor-forkjoin</code>, 
<code>akka-actor-forkjoin-2.5</code></td>
   <td><code>akka-actor-2.3</code></td>
   </tr>
   <tr>
   <td><code>akka-http-server-route</code></td>
   <td><code>akka-http-10.0</code></td>
   </tr>
   <tr>
   <td><code>annotations</code></td>
   <td><code>opentelemetry-instrumentation-annotations</code></td>
   </tr>
   <tr>
   <td><code>armeria-1.14</code></td>
   <td><code>armeria-grpc-1.14</code> for gRPC; <code>armeria</code> for the 
component</td>
   </tr>
   <tr>
   <td><code>aws-lambda-core</code>, <code>aws-lambda-events</code></td>
   <td><code>aws-lambda-core-1.0</code>, <code>aws-lambda-events-2.2</code>, 
respectively</td>
   </tr>
   <tr>
   <td><code>aws-sdk-1.11-core</code></td>
   <td><code>aws-sdk-1.11</code></td>
   </tr>
   <tr>
   <td><code>aws-sdk-1.11-sqs</code></td>
   <td><code>aws-sdk-sqs</code></td>
   </tr>
   </tbody>
   </table>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li>See full diff in <a 
href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commits";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha&package-manager=maven&previous-version=2.31.1-alpha&new-version=2.32.0-alpha)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to