opentelemetry-java-instrumentation icon indicating copy to clipboard operation
opentelemetry-java-instrumentation copied to clipboard

OpenTelemetry auto-instrumentation and instrumentation libraries for Java

Results 335 opentelemetry-java-instrumentation issues
Sort by recently updated
recently updated
newest added

Part of https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/12804

test native

### Is your feature request related to a problem? Please describe. currently in our application we are using `opentelemetry-okhttp-3.0` library but we don't wanted to use alpha tag and deliver,...

enhancement

**Describe the bug** When using nacos to refresh the configuration, the `OpenTelemetryDataSource` reports an error and the configuration refresh does not take effect **Steps to reproduce** Use pom.xml to import...

bug
spring boot starter

Hopefully resolves https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/13180 Since we keep the statement as key in the sanitization cache large statements can cause the cache to grow to several hundred mb in size. This PR...

### Is your feature request related to a problem? Please describe. Yes, sometimes users may serialize some Java bean, which may be instrumented by OpenTelemetry Java Agent. Java Agent may...

enhancement
needs triage

Context: GraalVM JVM 23 and OTel starter See the `AbstractOtelSpringStarterSmokeTest` updated in #13500

bug
needs triage

- adds `jvm.yaml` in the JMX library so it can be reused by [jmx-scraper in contrib](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/jmx-scraper). - adds documentation on the captured metrics and links to semconv, also include limitations....

Related to https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/13111. The host portion of the URL supports glob patterns.

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` -...

For some metrics like `jvm.cpu.time` and `jvm.cpu.recent_utilization`, the JVM can return a negative value as the underlying data might not be available as indicated by [`OperatingSystemMXBean.getCpuLoad()` javadoc](https://docs.oracle.com/en/java/javase/17/docs/api/jdk.management/com/sun/management/OperatingSystemMXBean.html#getCpuLoad()). This corner case...