jack-berg

Break out :exporters:common module

9

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

Use NoopLogEmitterBuilder when no log processors are registered

3

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

Allow logs to be mutated by LogProcessor

2

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

Move non-core components out of opentelemetry-java

25

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

Serialize resource attributes in target info for PrometheusHttpServer

11

Resolves #4552.

Default bucket boundaries for explicit bucket histogram are different from specification

1

The [java default](https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk/metrics/src/main/java/io/opentelemetry/sdk/metrics/internal/aggregator/ExplicitBucketHistogramUtils.java#L24-L25) explicit bucket histogram bucket boundaries are: `[5, 10, 25, 50, 75, 100, 250, 500, 750, 1_000, 2_500, 5_000, 7_500, 10_000]` But according to the [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#explicit-bucket-histogram-aggregation) should be:...

Prometheus exporter resource attributes

6

The [spec says](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/data-model.md#resource-attributes-1) the prometheus exporter SHOULD convert resource attributes to the target info metric family. We don't currently do this, but we should.

Noticed a test flake [here](https://github.com/open-telemetry/opentelemetry-java/runs/7431610099?check_suite_focus=true#step:5:1436): ``` OtlpGrpcRetryTest > configureLogExporterRetryPolicy() FAILED org.opentest4j.AssertionFailedError: [status code PERMISSION_DENIED should make 1 requests] expected: 1 but was: 0 at [email protected]/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at [email protected]/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at [email protected]/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)...

Reduce set of published artifacts

2

We publish a lot of artifacts, and it's cumbersome for users to sort through which are needed. There's opportunity to reduce the sprawl, partially made possible by the recent stabilization...

Append unit to prometheus metric names

1

The spec [requires](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/datamodel.md#metric-metadata-1) that unit be appended to the metric name as a suffix. We don't do that anywhere today. I believe that would represent a breaking behavior change for...