chore(deps): update dependency opentelemetry-java-instrumentation to v2.22.0 #885
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.21.0->2.22.0Release Notes
open-telemetry/opentelemetry-java-instrumentation (opentelemetry-java-instrumentation)
v2.22.0: Version 2.22.0Compare Source
This release targets the OpenTelemetry SDK 1.56.0.
Note that many artifacts have the
-alphasuffix 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.aws.bucket.name(S3) →aws.s3.bucket-aws.queue.url(SQS) →aws.sqs.queue.url-aws.stream.name(Kinesis) →aws.kinesis.stream_name-aws.table.name(DynamoDB) →aws.dynamodb.table_names-aws.dynamodb.provisioned_throughput.read_capacity_units→aws.dynamodb.provisioned_read_capacity(type changed from long to double) -aws.dynamodb.provisioned_throughput.write_capacity_units→aws.dynamodb.provisioned_write_capacity(type changed from long to double) -aws.dynamodb.exclusive_start_table_name→aws.dynamodb.exclusive_start_table-aws.dynamodb.projection_expression→aws.dynamodb.projection-aws.dynamodb.scan_index_forward→aws.dynamodb.scan_forward- The following attribute types have changed: -aws.dynamodb.table_names: string → string[] -aws.dynamodb.consumed_capacity: string → string[] -aws.dynamodb.global_secondary_indexes: string → string[] -aws.dynamodb.local_secondary_indexes: string → string[] -aws.dynamodb.consistent_read: string → boolean -aws.dynamodb.table_count: string → long -aws.dynamodb.limit: string → long -aws.dynamodb.attributes_to_get: string → string[] -aws.dynamodb.segment: string → long -aws.dynamodb.total_segments: string → long -aws.dynamodb.count: string → long -aws.dynamodb.scanned_count: string → long - The following attributes are no longer emitted by default but can be enabled withotel.instrumentation.aws-sdk.experimental-span-attributes=true: -aws.queue.name(SQS) -aws.lambda.function.name(Lambda) -aws.lambda.function.arn(Lambda)1to align with semantic conventions (#15093)otel.instrumentation.aws-sdk.experimental-span-attributes=true- The following attributes have been renamed and are now emitted by default (no experimental flag required): -aws.bucket.name(S3) →aws.s3.bucket-aws.queue.url(SQS) →aws.sqs.queue.url-aws.stream.name(Kinesis) →aws.kinesis.stream_name-aws.table.name(DynamoDB) →aws.dynamodb.table_names🚫 Deprecations
🌟 New javaagent instrumentation
📈 Enhancements
az.namespacecan be used for sampling (#15068)JmxTelemetryAPI for JMX metrics library (#15220)ExtendedOpenTelemetry(#15178)🛠️ Bug fixes
peer.servicein Netty HTTP spans (#14963)CLIENTinstead ofINTERNAL(#14995)@EnableAsync(#15249)StructuredArguments.entries()(#15341)🙇 Thank you
This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:
@bioplasticlining
@breedx-splk
@brunobat
@copilot-pull-request-reviewer
@defields923
@dixanms
@jack-berg
@jaydeluca
@jeanbisutti
@JonasKunz
@kasiditi
@koksay
@Kresshy
@laurit
@LikeTheSalad
@lukaszgryglicki
@mateuszrzeszutek
@mlbiscoc
@mznet
@PaarthB
@pepeshore
@roberttoyonaga
@robsunday
@steverao
@SylvainJuge
@tharsanrp
@trask
@vasireddy99
@wyctxwd1
@zeitlinger
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.