fix(deps): update otel-instrumentation #714
Open
+2
−2
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.24.02.21.0-alpha->2.24.0-alpha2.21.0-alpha->2.24.0-alphaRelease Notes
open-telemetry/opentelemetry-java-instrumentation (io.opentelemetry.instrumentation:opentelemetry-instrumentation-api)
v2.24.0otel.instrumentation.logback-appender.experimental.capture-logstash-attributes(#15722)
(#15802)
🚫 Deprecations
addClassPathRulesandaddCustomRulesmethods inJmxTelemetryBuilder, and moved non-public classes to an internal package(#15658)
setMessagingReceiveInstrumentationEnabledin favor ofsetMessagingReceiveTelemetryEnabledto match config property name(#15668)
getDbSystem()andgetResponseStatus()in favor of
getDbSystemName()andgetResponseStatusCode()to align with stable semanticconventions
(#15696)
setCapturedRequestParameters()in Servlet library instrumentation in favor ofExperimental.setCapturedRequestParameters()as request parameter capture is experimental(#15826)
getHttpClient(),setHttpClientTransport(), andsetSslContextFactory()in Jettyclient instrumentation in favor of new builder-style methods
newHttpClient(),newHttpClient(SslContextFactory), andnewHttpClient(HttpClientTransport, SslContextFactory)(#15827)
(#15828)
newHttpClient()in favor ofwrap()in Java HTTP Client instrumentation forconsistency with naming conventions across library instrumentations
(#15829)
new*methods in favor ofcreate*methods across multiple instrumentation librariesfor consistency (e.g.,
newHttpClient()→createHttpClient(),newInterceptor()→createInterceptor())(#15832)
SqlStatementInfoandMultiQueryin favor of methods using stablesemantic convention terminology:
getFullStatement()→getQueryText(),getOperation()→getOperationName(), andgetStatements()→getQueryTexts()(#15833)
terminology:
getResponseStatusCode()→getDbResponseStatusCode(),getBatchSize()→getDbOperationBatchSize(), andgetQueryParameters()→getDbQueryParameters()(#15859)
📈 Enhancements
otel.instrumentation.logback-appender.experimental.capture-template(#15649)
(#15684)
(#15656,
#15688,
#15697,
#15698,
#15704,
#15707,
#15713,
#15714,
#15722,
#15727,
#15732,
#15733,
#15734,
#15735,
#15740,
#15741,
#15742,
#15752,
#15756,
#15787,
#15791,
#15792,
#15841,
#15856)
us.,global.) forinference profiles
(#15751)
(#15797)
setSpanNameExtractorCustomizer(#15825)
(#15836,
#15854)
SpanStatusExtractor.extract()beforeOperationListener.onEnd()inInstrumenter(#15844)
🛠️ Bug fixes
enduser.id(#15858)
(#15682)
v2.23.0with semantic conventions (see PR description for specifics)
(#14996)
(#15324)
captureArgumentsno longer captures message template, usecaptureTemplate(#15423)
re-enable with
otel.instrumentation.common.experimental.controller-telemetry.enabled=true(#15604)
🚫 Deprecations
setSpanNameExtractor()andsetStatusExtractor()in favor of
setSpanNameExtractorCustomizer()andsetStatusExtractorCustomizer()(#15529)
🌟 New javaagent instrumentation
(#14933)
🌟 New library instrumentation
(#15114)
(#15473)
📈 Enhancements
(#14917)
RetryPolicy(#15255,
#15537)
(#15384)
(#15413)
(#15433)
(#15434)
(#15459)
ClientResources(#15470)
(#15472)
(#15476)
trace_idandspan_idattributes to requests(#15485)
(#15499)
(#15500)
(#15502,
#15574)
(#15525)
(#15540)
(#15592)
(#15620)
🛠️ Bug fixes
(#15306)
afterRecordcallback(#15367)
(#15424)
end()calls inKtorServerTelemetry(#15452)
ExtendedOpenTelemetrydeclarative config(#15478)
http.routeattribute capture and span naming(#15504)
InstrumenterCustomizerProviderand related classes(#15538)
(#15607)
v2.22.0(#15028)
aws.bucket.name(S3) →aws.s3.bucketaws.queue.url(SQS) →aws.sqs.queue.urlaws.stream.name(Kinesis) →aws.kinesis.stream_nameaws.table.name(DynamoDB) →aws.dynamodb.table_namesaws.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_tableaws.dynamodb.projection_expression→aws.dynamodb.projectionaws.dynamodb.scan_index_forward→aws.dynamodb.scan_forwardaws.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 → booleanaws.dynamodb.table_count: string → longaws.dynamodb.limit: string → longaws.dynamodb.attributes_to_get: string → string[]aws.dynamodb.segment: string → longaws.dynamodb.total_segments: string → longaws.dynamodb.count: string → longaws.dynamodb.scanned_count: string → longotel.instrumentation.aws-sdk.experimental-span-attributes=true:aws.queue.name(SQS)aws.lambda.function.name(Lambda)aws.lambda.function.arn(Lambda)(#15074)
1to align with semantic conventions(#15093)
(#15094)
otel.instrumentation.aws-sdk.experimental-span-attributes=trueaws.bucket.name(S3) →aws.s3.bucketaws.queue.url(SQS) →aws.sqs.queue.urlaws.stream.name(Kinesis) →aws.kinesis.stream_nameaws.table.name(DynamoDB) →aws.dynamodb.table_names(#15118)
(#15247)
(#15261)
🚫 Deprecations
(#14929)
(#15101)
(#15139)
🌟 New javaagent instrumentation
(#15216)
📈 Enhancements
(#14855,
#15091)
az.namespacecan be used for sampling(#15068)
(#15132)
(#15144)
(#15195)
(#15227)
(#15287,
#15299,
#15301,
#15304,
#15311,
#15362,
#15371)
(#15288)
(#15169)
(#15289)
(#15217)
JmxTelemetryAPI for JMX metrics library(#15220)
ExtendedOpenTelemetry(#15178)
🛠️ Bug fixes
peer.servicein Netty HTTP spans(#14963)
CLIENTinstead ofINTERNAL(#14995)
(#15143)
(#15231)
@EnableAsync(#15249)
(#15260)
StructuredArguments.entries()(#15341)
(#15336)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.