jack-berg

As reported by @laurit, `Span#setStatus` [implementation](https://github.com/open-telemetry/opentelemetry-java/blob/8194c10b785b7f8d232b4bce0b5f70c91669201a/sdk/trace/src/main/java/io/opentelemetry/sdk/trace/SdkSpan.java#L420) doesn't conform to the [spec](https://github.com/open-telemetry/opentelemetry-specification/blame/0a78571045ca1dca48621c9648ec3c832c3c541c/specification/trace/api.md#L563-L590). Notably: - Status codes form a priority of `OK > ERROR > UNSET`, where a call to set a...

Stabilize `otel.experimental.resource.disabled.keys`

4

As discussed in this [comment](https://github.com/open-telemetry/opentelemetry-java/issues/6772#issuecomment-2405263383), `otel.experimental.resource.disabled.keys` has been experimental for a while - introduced in #4169 on 2/17/2022. It seems both important and correctly modeled. We should stabilize it.

Limit prometheus exemplar label characters to conform to prometheus limits

3

> I ran the agent using java auto-instrument. Everything seemed to be working fine, but I didn't see any exemplar in grafana. I checked the error below through the prometheus...

SimpleLogRecordProcessor, SimpleSpanProcessor call export concurrently, but shouldn't

1

`SpanExporter#export`, `LogRecordExporter#export` [should not be called concurrently](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#exportbatch), but `SimpleSpanProcessor`, `SimpleLogRecordExporter` don't have any synchronization: https://github.com/open-telemetry/opentelemetry-java/blob/ee7fd2744949ae0c060d28c73edfca56633dc170/sdk/trace/src/main/java/io/opentelemetry/sdk/trace/export/SimpleSpanProcessor.java#L84-L102 https://github.com/open-telemetry/opentelemetry-java/blob/ee7fd2744949ae0c060d28c73edfca56633dc170/sdk/logs/src/main/java/io/opentelemetry/sdk/logs/export/SimpleLogRecordProcessor.java#L63-L79 Noted by @pellared in https://github.com/open-telemetry/opentelemetry-specification/issues/4134#issuecomment-2218883965

Demonstrates how declarative config is integrated with the otel java agent and can be used to configure instrumentations. Related to: https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/12265

Declarative config: clarify null vs empty

1

Fixes #4181 cc @open-telemetry/configuration-approvers

How to reflect experimental features to spec compliance matrix

5

As discussed in the 4/2/24 Spec SIG, the [spec compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md) is ambiguous in terms of how to represent experimental features: - Should experimental features be given rows? - How...

Event API calls should loop back to log frameworks without cycles

4

Currently, there are two sources of data for the log SDK: 1. Log appenders for log4j, logback, etc bridge log records recorded via their respective APIs: ``` log framework ->...

The file config spec [says](https://github.com/open-telemetry/opentelemetry-specification/blame/5381b55dd8e6adcbf99e153533e5ad8ea3dd6b38/specification/configuration/file-configuration.md#L297): > Parse MUST interpret null as equivalent to unset. This has led to some confusion (see [discussion 1](https://github.com/open-telemetry/opentelemetry-specification/pull/4128#discussion_r1705113363)) and could use clarification. Let's illustrate the...

Use ABNF syntax instead of PCRE2 in file configuration env var substitution syntax

1

> There was a discussion in the config working group this week to use ABNF (https://en.wikipedia.org/wiki/Augmented_Backus%E2%80%93Naur_form) notation in the spec instead of PCRE2 to leave it up to implementations as...