Trask Stalnaker
Trask Stalnaker
Calling `BlobClientBase.exists()` produces two spans (which is expected): an INTERNAL span: > SpanData{spanContext=ImmutableSpanContext{traceId=92c3d060568c79c1fafbc818297ea4af, spanId=b98cca7f7c875f09, traceFlags=01, traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true}, parentSpanContext=ImmutableSpanContext{traceId=00000000000000000000000000000000, spanId=0000000000000000, traceFlags=00, traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=false}, resource=Resource{schemaUrl=null, attributes={service.name="unknown_service:java", telemetry.sdk.language="java", telemetry.sdk.name="opentelemetry", telemetry.sdk.version="1.42.1"}}, instrumentationScopeInfo=InstrumentationScopeInfo{name=azure-storage-blob,...
Currently blocked on test failures in `VariousCollectorsTest` cc @jeanbisutti
Hi! Over in the OpenTelemetry Java Instrumentation project, we got a report about our project causing OOM when instrumenting xxl-rpc's netty usage (https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/11942). We have mitigated the OOM (https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/12003), but...
Using [find-all-config-properties.sh](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/.github/scripts/find-all-config-properties.sh) -- Config properties with the word `experimental`: - `otel.instrumentation.apache-shenyu.experimental-span-attributes` - `otel.instrumentation.aws-sdk.experimental-record-individual-http-error` - `otel.instrumentation.aws-sdk.experimental-span-attributes` - `otel.instrumentation.aws-sdk.experimental-use-propagator-for-messaging` - `otel.instrumentation.camel.experimental-span-attributes` - `otel.instrumentation.common.experimental.controller-telemetry.enabled` - `otel.instrumentation.common.experimental.view-telemetry.enabled` - `otel.instrumentation.couchbase.experimental-span-attributes` - `otel.instrumentation.elasticsearch.experimental-span-attributes` - `otel.instrumentation.experimental.span-suppression-strategy` -...
Database semantic convention stability implementation tracking issue - [x] #11575 - [x] #12601 - [ ] Use `OTEL_SEMCONV_RC_OPT_IN` instead of `OTEL_SEMCONV_STABILITY_OPT_IN` until database semconv is actually marked stable to avoid...
This is similar to HttpClientAttributesGetter, and generally simplifies usage because the related Extractors can be all managed internally by DbClientAttributesExtractor. Built on top of #12602 for now
Proposal, related to #932