jack-berg

Opamp spec overloads definition of service.name

13

[AgentDescription.identifying_attributes](https://github.com/open-telemetry/opamp-spec/blob/main/specification.md#agentdescriptionidentifying_attributes) says the following about `service.name`: > service.name should be set to a reverse FQDN that uniquely identifies the Agent type, e.g. "io.opentelemetry.collector" This definition contradicts the `service.name` definition in...

Delete prometheus-client-bridge

5

### Component(s) prometheus-client-bridge ### What happened? The functionality is implemented in `opentelemetry-java` in https://github.com/open-telemetry/opentelemetry-java/pull/6015, which allows you to associate your own `PrometheusRegistry` with `PrometheusHttpServer`. ### Component version latest ### Log...

A prototype solution for #6197. The idea is to start to more fully realize the potential of scope as a concept. Today, scope is just a piece of metadata attached...

Turn off spans from a scope while retaining downstream spans and without breaking traces

4

Suppose you have a span hierarchy of ({tracerName}:{spanKind}:{spanName}): ``` tracerA:server:parent -> tracerB:internal:child -> tracerC:client:grandchild ``` And you decide that internal spans from `tracerB` are too noisy. You want to turn...

Add connectTimeout configuration option OtlpGrpc{Signal}Exporters

2

Followup to #5941 which adds support for OTLP gRPC exporters.

Investigate feasibility of zero-allocation protobuf marshalers

1

The [OTLP protobuf marshalers](https://github.com/open-telemetry/opentelemetry-java/tree/main/exporters/otlp/common/src/main/java/io/opentelemetry/exporter/internal/otlp) maintain a bunch of state as they transform `SpanData`, `MetricData`, `LogRecordData` to an intermediate representation before serializing. We should investigate whether we can eliminate this state...

Extended config properties

4

Replaces draft #5873. @open-telemetry/java-instrumentation-maintainers in the 9/21 Java SIG meeting I brought up bringing the file configuration prototype into the java agent, and received feedback that it will be important...

Merge opentelemetry-api-events into opentelemetry-extension-incubator

3

> Writing this made me realize that its silly that we incubate APIs in both `opentelemetry-api-events` and `opentelemetry-extension-incubator`. I propose we merge events into `opentelemetry-extension-incubator`, and do it in lockstep...

Add get{Signal}Exporter methods to Simple{Signal}Processor, Batch{Signal}Processor

5

Originally discussed in this [comment](https://github.com/open-telemetry/opentelemetry-java/pull/5986#discussion_r1412295799), the idea is to make `AutoConfigurationCustomizer#addSpanProcessorCustomizer` more useful by allowing you to extract the configured SpanExporter/LogRecordExporter from the processor, and plug it into your own...