opentelemetry-java
opentelemetry-java copied to clipboard
OpenTelemetry Java SDK
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 3.1.0 to 3.1.1. Release notes Sourced from docker/build-push-action's releases. v3.1.1 Fix GitHub token not passed with Git context if subdir defined by @crazy-max (#663) Replace deprecated fs.rmdir...
Related to [comment](https://github.com/open-telemetry/opentelemetry-java/pull/4501#issuecomment-1170324564) in #4501. Unfortunately, we still need to keep `:exporters:otlp:common` since the serialization logic is used in `:expoters:logging-otlp`.
Currently if no log processors are registered, a `NoopLogProcessor` is used. This drops emitted log records, but the log sdk can still use memory to maintain the map of instrumentation...
**Is your feature request related to a problem? Please describe.** We're currently using the Zipkin exporter in Splunk's Android RUM instrumentation library. By default, the exporter will attach the device's...
**Describe the bug** We are using the following span exporter configuration ``` UdpSender thriftSender = new UdpSender(agentHostname, agentPort, ThriftUdpTransport.MAX_PACKET_SIZE); SpanExporter exporter = JaegerThriftSpanExporter.builder() .setThriftSender(thriftSender).build(); BatchSpanProcessor .builder(exporter) .build(); ``` This configuration...
Add to `io.opentelemetry.sdk.extension.aws.resource.EcsResource` the logic to detect the [`aws.ecs.*` resource attributes](https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/cloud_provider/aws/ecs/) using data from the Amazon ECS Metadata v4 endpoint.
Implements spec [PR#2681](https://github.com/open-telemetry/opentelemetry-specification/pull/2681). Resolves #4550. Summary: - Rename `LogBuilder` to `LogRecordBuilder` to better reflect the data model and the naming we can expect to see in the log appender /...
Following the spirit of moving [opentelemetry-extension-annotations](https://github.com/open-telemetry/opentelemetry-java/pull/4659) to a more appropriate home in `opentelemetry-java-instrumentation`, and prompted by a discussion in the 7/28 Office Hours, I've done a scan of the project...