search

eclipse / microprofile-telemetry

microprofile telemetry
Apache License 2.0
16 stars 16 forks source link

Bump io.opentelemetry.instrumentation:opentelemetry-logback-appender-1.0 from 2.2.0-alpha to 2.5.0-alpha #189

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps io.opentelemetry.instrumentation:opentelemetry-logback-appender-1.0 from 2.2.0-alpha to 2.5.0-alpha.

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-logback-appender-1.0's releases.

Version 2.4.0

This release targets the OpenTelemetry SDK 1.38.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they are still alpha quality and will continue to have breaking changes. Please see the VERSIONING.md for more details.

🌟 New javaagent instrumentation

📈 Enhancements

  • Instrument ConnectionSource in Akka/Pekko HTTP Servers (#11103)
  • Use constant span name when using Spring AMQP AnonymousQueues (#11141)
  • Add support for RestClient in Spring starter (#11038)
  • Add support for WebFlux server in Spring starter (#11185)
  • Add async operation end strategy for Kotlin coroutines flow (#11168)
  • Add automatic JDBC instrumentation to the Spring starter (#11258)
  • Add StructuredTaskScope instrumentation (#11202)
  • Allow reading OTel context from reactor ContextView (#11235)
  • Add spring starter r2dbc support (#11221)
  • Enable instrumentation of Spring EJB clients (#11104)
  • Support otel.instrumentation.kafka.experimental-span-attributes in Spring starter (#11263)
  • Remove incubating semconv dependency from library instrumentation (#11324)
  • Add extension functions for Ktor plugins (#10963)
  • Add dedicated flag for R2DBC statement sanitizer (#11384)
  • Allow library instrumentations to override span name (#11355)
  • Don't sanitize PostgreSQL parameter markers (#11388)
  • Make statement sanitizer configurable for Spring Boot (#11350)

🛠️ Bug fixes

  • Fix GraphQL instrumentation to work with latest version (#11142)
  • Fix jmx-metrics on WildFly (#11151)
  • End gRPC server span in onComplete instead of close (#11170)
  • Fix a bug in undertow instrumentation related to HTTP/2 (#11361)
  • Armeria http client reports wrong protocol version (#11334)
  • Use daemon thread for scheduling in jmx-metrics BeanFinder (#11337)

🙇 Thank you

This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:

@​123liuziming @​aaron-ai @​AlchemyDing @​ArtyomGabeev @​aschugunov @​breedx-splk

... (truncated)

Changelog

Sourced from io.opentelemetry.instrumentation:opentelemetry-logback-appender-1.0's changelog.

Changelog

Unreleased

Version 2.5.0 (2024-06-17)

📈 Enhancements

  • Add support for Informix connection string parsing in JDBC instrumentation (#11542)
  • Generate an SBOM for the javaagent artifact (#11075)
  • Extract sql operation even when the sanitizer is disabled (#11472)
  • Improve security manager support (#11466)
  • Generate Log4j2Plugin.dat for OpenTelemetryAppender (#11503)
  • Stop kotlin coroutine dispatcher from propagating context (#11500)
  • Handle Vert.x sub routes (#11535)
  • Undertow: run response customizer on all ServerConnection implementations (#11539)
  • Allow configuring MDC key names for trace_id, span_id, trace_flags (#11329)
  • Apply async end strategy to all kotlin coroutine flows (#11583)

🛠️ Bug fixes

  • Fix container.id issue in some crio scenarios (#11382)
  • Fix Finagle http client context propagation (#11400)
  • Fix sporadically failing finagle test (#11441)
  • Fix request header capture corrupting tomcat request (#11469)
  • Fix Ktor server instrumentation when Ktor client library is not present (#11454)
  • Fix gRPC instrumentation adding duplicates to metadata instead of overwriting (#11308)
  • Avoid NullPointerException when JMS destination is not available (#11570)
  • Fix Spring Kafka instrumentation closing the trace too early (#11471)

Version 1.33.3 (2024-05-21)

... (truncated)

Commits


Dependabot compatibility score

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 commands and options
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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show 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)
dependabot[bot] commented 1 week ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.