Mateusz Rzeszutek

Configure the `ZipkinSpanExporter` not to set the local IP address

1

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

Zipkin span exporter does not serialize arrays as JSON

6

**Describe the bug** The [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk_exporters/zipkin.md#attribute) mentions that arrays must be serialized to string as a JSON list: > Array values MUST be serialized to string like a JSON list as...

Consider making faas.id a span attribute instead of a resource attribute

16

**What are you trying to achieve?** Currently `faas.id` is a resource attribute. In AWS Lambda functions its value (lambda function ARN) is only available as a property of the AWS...

Configuring histograms in the API (hints?)

3

**What are you trying to achieve?** I'm working on the micrometer->OTel bridge instrumentation in the javaagent. Some of the micrometer instruments translate to OTel concepts in a rather straightforward way,...

Allow to unregister/stop/destroy instruments

19

**What are you trying to achieve?** I'm currently working on the micrometer->OTel bridge instrumentation in the javaagent. Micrometer offers the possibility to remove a meter from the `MeterRegistry` and stop...

Support for Splunk OpenTelemetry Java Instrumentation

5

Hi, I want to add a new framework that adds [Splunk OTel instrumentation agent](https://github.com/signalfx/splunk-otel-java) support. The agent collects telemetry sends it usually to either [OpenTelemetry collector](https://github.com/open-telemetry/opentelemetry-collector) or the [SignalFX Smart...

Segmentation error vmState=0x00053cff

6

Java -version output -------------------- ``` openjdk version "18.0.2" 2022-07-19 IBM Semeru Runtime Open Edition 18.0.2.0 (build 18.0.2+9) Eclipse OpenJ9 VM 18.0.2.0 (build openj9-0.33.0, JRE 18 Linux amd64-64-Bit Compressed References 20220804_30...

Clarify the HTTP client `http.retry_count` spec

8

Fixes #2737 ## Changes Clarifies when the `http.retry_count` attribute should be added to the HTTP client span (every time the HTTP request gets re-sent, no matter what the cause is)....

Should `http.server.active_requests` have a `net.host.port` attribute?

1

**What are you trying to achieve?** Currently, the `http.server.active_requests` metric only includes the `net.host.name` attribute; for some reason `net.host.port` was skipped there. Should we fix that discrepancy? **Additional context.** https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/http-metrics.md#attributes

HTTP retry spec clarification needed

3

**What are you trying to achieve?** I started working on implementing the HTTP retry spec in the Java HTTP client instrumentations, and I ran into several questions that I'd like...