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

   Bumps 
[io.opentelemetry.instrumentation:opentelemetry-log4j-appender-2.17](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-log4j-appender-2.17'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-log4j-appender-2.17's
 changelog</a>.</em></p>
   <blockquote>
   <h1>Changelog</h1>
   <h2>Unreleased</h2>
   <h3>⚠️ Breaking changes</h3>
   <ul>
   <li>Remove 
<code>otel.instrumentation.grpc.capture-metadata.client.request</code> and
   <code>otel.instrumentation.grpc.capture-metadata.server.request</code>.
   Use <code>otel.instrumentation.grpc.client.request-metadata.included</code> 
and
   <code>otel.instrumentation.grpc.server.request-metadata.included</code>.
   For declarative configuration, replace 
<code>java.grpc.capture_metadata.client.request</code> and
   <code>java.grpc.capture_metadata.server.request</code> with 
<code>java.grpc.client.request_metadata.included</code> and
   <code>java.grpc.server.request_metadata.included</code>.</li>
   <li>Captured messaging header attribute keys now preserve dashes 
unconditionally; for example,
   <code>messaging.header.Test_Message_Id</code> is now 
<code>messaging.header.Test-Message-Id</code>. Replace
   
<code>otel.instrumentation.messaging.experimental.headers.included=Test-Message-*</code>
 with
   
<code>otel.instrumentation.common.messaging.headers.included=Test-Message-*</code>.
   The deprecated 
<code>otel.instrumentation.messaging.experimental.headers.included</code>,
   <code>otel.instrumentation.messaging.experimental.headers.excluded</code>, 
and
   <code>otel.instrumentation.messaging.experimental.capture-headers</code> 
settings are no longer supported;
   use <code>otel.instrumentation.common.messaging.headers.included</code> / 
<code>.excluded</code> instead.
   
<code>otel.instrumentation.messaging.experimental.receive-telemetry.enabled</code>
 is also no longer
   supported; use 
<code>otel.instrumentation.common.messaging.experimental.receive-telemetry.enabled</code>.</li>
   <li>OSHI system metrics use schema version 1.44.0 and scope 
<code>io.opentelemetry.oshi-5.0</code>.
   Update <code>system.network.packets</code> to 
<code>system.network.packet.count</code>, plural count units to
   <code>{packet}</code>, <code>{error}</code>, and <code>{operation}</code>. 
Replace memory <code>state</code> with <code>system.memory.state</code>;
   for network I/O and errors, replace <code>device</code> and 
<code>direction</code> with <code>network.interface.name</code>
   and <code>network.io.direction</code>. Packet counts use 
<code>system.device</code> and <code>network.io.direction</code>;
   disk metrics use <code>system.device</code> and 
<code>disk.io.direction</code>.
   Remove <code>otel.instrumentation.oshi.experimental-metrics.enabled</code>; 
OSHI no longer emits <code>runtime.java.memory</code>
   or <code>runtime.java.cpu_time</code>. <code>jvm.memory.used</code> measures 
JVM pools, not process RSS or virtual
   memory, and <code>jvm.cpu.time</code> does not split user/system CPU 
time.</li>
   <li>Remove the deprecated GraphQL configuration properties
   
<code>otel.instrumentation.graphql.add-operation-name-to-span-name.enabled</code>
 and
   <code>otel.instrumentation.graphql.query-sanitizer.enabled</code>. Use
   
<code>otel.instrumentation.graphql.operation-name-in-span-name.enabled</code> 
and
   <code>otel.instrumentation.graphql.query-sanitization.enabled</code>, 
respectively.</li>
   <li>The Java agent and standalone libraries now use the existing v1.43.0 
messaging implementation.</li>
   <li>Remove support for the deprecated controller and view telemetry aliases. 
Replace
   
<code>otel.instrumentation.common.experimental.controller-telemetry.enabled</code>
 and
   <code>otel.instrumentation.common.experimental.view-telemetry.enabled</code> 
with
   <code>otel.instrumentation.common.controller-telemetry.enabled</code> and
   <code>otel.instrumentation.common.view-telemetry.enabled</code>.</li>
   <li>Emit only stable source code attributes: <code>code.function.name</code> 
replaces <code>code.namespace</code> and
   <code>code.function</code>, and log records use <code>code.file.path</code> 
and <code>code.line.number</code> instead of
   <code>code.filepath</code> and <code>code.lineno</code>. The 
<code>code</code> and <code>code/dup</code> opt-ins and
   <code>general.code.semconv</code> declarative settings no longer select 
legacy emission.</li>
   <li>Change the Java agent's <code>telemetry.distro.name</code> resource 
attribute from
   <code>opentelemetry-java-instrumentation</code> to 
<code>opentelemetry-javaagent</code>.</li>
   <li>Database telemetry now uses schema version 1.44.0.</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-log4j-appender-2.17&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]

Reply via email to