aws-observability / aws-otel-community

Welcome to the AWS Distro for OpenTelemetry project. If you're using monitoring and observability tools for AWS products and services, this is a great place to ask questions, request features and network with other community members.
https://aws-otel.github.io/
Apache License 2.0
96 stars 96 forks source link

Bump the centralized-integration-deps group across 1 directory with 4 updates #1147

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 2 months ago

Bumps the centralized-integration-deps group with 4 updates in the /centralized-sampling-tests/integration-tests directory: io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha, io.opentelemetry.contrib:opentelemetry-aws-xray, com.jayway.jsonpath:json-path and io.spring.dependency-management.

Updates io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha from 1.32.0-alpha to 2.7.0-alpha

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha's releases.

Version 2.6.0

This release targets the OpenTelemetry SDK 1.40.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.

The Spring Boot Starter (opentelemetry-spring-boot-starter) is now stable.

Migration notes

  • The opentelemetry-spring-boot and opentelemetry-spring-boot-3 artifacts have been merged into a single artifact named opentelemetry-spring-boot-autoconfigure which supports both Spring Boot 2 and Spring Boot 3
  • Two experimental HTTP metrics have been renamed: - http.server.request.sizehttp.server.request.body.size, - http.server.response.sizehttp.server.response.body.size

🌟 New javaagent instrumentation

📈 Enhancements

  • Support HTTP client instrumentation configuration in Spring starter (#11620)
  • Influxdb client: don't fill db.statement for create/drop database and write operations (#11557)
  • Support otel.instrumentation.common.default-enabled in the Spring starter (#11746)
  • Support Jetty HTTP client 12 (#11519)
  • Add Pulsar messaging.producer.duration metric (#11591)
  • Improve instrumentation suppression behavior (#11640)
  • Propagate OpenTelemetry context through custom AWS client context for Lambda direct calls (#11675)
  • Spring Native support for @WithSpan (#11757)
  • Support HTTP server instrumentation config properties in the Spring starter (#11667)

🛠️ Bug fixes

  • Fix http.server.active_requests metric with async requests (#11638)

🙇 Thank you

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

@​123liuziming @​breedx-splk @​crossoverJie @​devurandom @​heyams @​jaydeluca @​jeanbisutti @​johnbley @​JonasKunz @​laurit @​lucasamoroso @​pandaji @​steverao

... (truncated)

Changelog

Sourced from io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha's changelog.

Changelog

Unreleased

Version 2.7.0 (2024-08-16)

📈 Enhancements

  • Add span baggage processor (#11697)
  • Improve tomcat version detection (#11936)
  • Improve akka route handling with java dsl (#11926)
  • Ignore Alibaba fastjson ASMClassLoader (#11954)
  • Use aws-lambda-java-serialization library, which is available by default, while deserializing input and serializing output (#11868)
  • Logback appender: map timestamp in nanoseconds if possible (#11974)
  • Save ILoggingEvent.getArgumentArray() arguments from Logback (#11865)
  • Update Java 17-based metrics to stable semconv (#11914)
  • Add Pulsar Consumer metrics (#11891)

🛠️ Bug fixes

  • Fix missing throw statement in RestClientWrapper (#11893)
  • Fix ClickHouse tracing when database name not included in connection string (#11852)
  • Fix class cast exception, noop meter does not implement incubating API (#11934)
  • Closing a kafka producer/consumer should not disable metrics from other consumers/producers (#11975)
  • Fix ending span in Ktor plugin (#11726)
  • Fix netty memory leak (#12003)

Version 1.33.5 (2024-07-25)

📈 Enhancements

  • Backport: Update the OpenTelemetry SDK version to 1.40.0 (#11879)

Version 2.6.0 (2024-07-17)

... (truncated)

Commits


Updates io.opentelemetry.contrib:opentelemetry-aws-xray from 1.32.0 to 1.38.0

Release notes

Sourced from io.opentelemetry.contrib:opentelemetry-aws-xray's releases.

Version 1.38.0

This release targets the OpenTelemetry Java Instrumentation 2.7.0.

JFR connection

  • Recording close should not throw exception (#1412)

🙇 Thank you

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

@​breedx-splk @​dehaansa @​dsgrieve @​jack-berg @​laurit @​PeterF778 @​trask

Version 1.37.0

This release targets the OpenTelemetry SDK 1.40.0.

AWS resources

  • Add ECS cluster detection (#1354)

Baggage processor

  • Add config support (#1330)

Inferred spans - New 🌟

An OpenTelemetry extension for generating spans via profiling instead of instrumentation. This extension enhances traces by running async-profiler in wall-clock profiling mode whenever there is an active sampled OpenTelemetry span.

The resulting profiling data is analyzed afterward and spans are "inferred". This means there is a delay between the regular and the inferred spans being visible in your OpenTelemetry backend/UI.

JFR connection

  • Fix for using diagnostic command to start a recording (#1352)

JMX metrics

  • Support both a script and target systems (#1339)

🙇 Thank you

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

@​bjrara @​breedx-splk

... (truncated)

Changelog

Sourced from io.opentelemetry.contrib:opentelemetry-aws-xray's changelog.

Version 1.38.0 (2024-08-19)

JFR connection

  • Recording close should not throw exception (#1412)

Version 1.37.0 (2024-07-18)

AWS resources

  • Add ECS cluster detection (#1354)

Baggage processor

  • Add config support (#1330)

Inferred spans - New 🌟

An OpenTelemetry extension for generating spans via profiling instead of instrumentation. This extension enhances traces by running async-profiler in wall-clock profiling mode whenever there is an active sampled OpenTelemetry span.

The resulting profiling data is analyzed afterward and spans are "inferred". This means there is a delay between the regular and the inferred spans being visible in your OpenTelemetry backend/UI.

JFR connection

  • Fix for using diagnostic command to start a recording (#1352)

JMX metrics

  • Support both a script and target systems (#1339)

Version 1.36.0 (2024-05-29)

AWS resources

  • Optimization: don't attempt detection if a cloud provider has already been detected (#1225)

Baggage processor - New 🌟

This module provides a SpanProcessor that stamps baggage onto spans as attributes on start.

... (truncated)

Commits
  • 4c22b8b [release/v1.38.x] Fix incorrect SDK version included in release notes (#1428)
  • 25efd3c [release/v1.38.x] Prepare release 1.38.0 (#1425)
  • cf1490e Update change log (#1419)
  • 829ad73 Update dependency com.gradle.enterprise:com.gradle.enterprise.gradle.plugin t...
  • adcc624 Update plugin com.gradle.develocity to v3.18 (#1423)
  • b9fd5fa Update dependency org.apache.maven.plugin-tools:maven-plugin-annotations to v...
  • 6e3f837 Update dependency com.google.guava:guava-bom to v33.3.0-jre (#1420)
  • 179e5fd Update dependency io.opentelemetry.instrumentation:opentelemetry-instrumentat...
  • 1942659 jfr-connection: Recording close should not throw exception (#1412)
  • cf3589e Update errorProneVersion to v2.30.0 (#1408)
  • Additional commits viewable in compare view


Updates com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0

Release notes

Sourced from com.jayway.jsonpath:json-path's releases.

json-path-2.9.0

What's Changed

New Contributors

Full Changelog: https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0

Commits


Updates io.spring.dependency-management from 1.1.4 to 1.1.6

Release notes

Sourced from io.spring.dependency-management's releases.

v1.1.6

:lady_beetle: Bug Fixes

  • Applying Maven-style exclusions may cause a deprecation warning with Gradle 8.8 #384

:heart: Contributors

Thank you to all the contributors who worked on this release:

@​quaff

v1.1.5

:lady_beetle: Bug Fixes

  • When a dependency has been substituted by changing its target, its version is managed based on its original group and artifact IDs #383
  • Plugin triggers a deprecation warning for LenientConfiguration#getArtifacts(Spec) with Gradle 8.8 #381
  • Exclusions are calculated unnecessarily for non-transitive configurations #372

:heart: Contributors

Thank you to all the contributors who worked on this release:

@​fp7

Commits
  • 57d4a77 Release v1.1.6
  • caad92a Apply exclusions earlier to avoid deprecation warning
  • 68f86ea Merge pull request #387 from quaff
  • 4d44a45 Remove stray backtick
  • 90d9e1a Rename property to address naming clash
  • 3c2f6e7 Next development version (v1.1.6-SNAPSHOT)
  • 70f3e08 Release from GitHub Actions
  • b5ed22b Correct the value of build-name when deploying to Artifactory
  • 029d266 Specify the shell for build and publish step
  • 2ddde6f Prepare snapshot workflow for addition of release workflow
  • Additional commits viewable in compare view


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 major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 1 month ago

Superseded by #1171.