Robert Pająk

Log record mutations are visible in next registered processors

17

**What are you trying to achieve?** Define if log record mutations done in record processor are visible in next registered processors. From https://github.com/open-telemetry/opentelemetry-specification/issues/4010#issuecomment-2100878288: > I believe the spec is not...

Clarify: the timestamp when a metric collection system started

7

**What are you trying to achieve?** Set appropriate value of `start_time_unix_nano` for gauge: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/data-model.md#gauge > (optional) A timestamp (`start_time_unix_nano`) which best represents the first possible moment a measurement could be...

Clarify OTLP/gRPC endpoint configuration option handling

6

I've had users ask why the path is ignored for gRPC. Its not clear to new gRPC users that the path is derived from the proto spec for the service....

OTLP exporters should not percent decode the key when parsing HEADERS env vars

3

The OTLP exporters SHOULD NOT percent decode the header keys when parsing `OTEL_EXPORTER_OTLP_HEADERS`, `OTEL_EXPORTER_OTLP_TRACES_HEADERS`, `OTEL_EXPORTER_OTLP_METRICS_HEADERS`, `OTEL_EXPORTER_OTLP_LOGS_HEADERS` env vars. Moreover, only valid header keys should be parsed. Current behavior: https://github.com/open-telemetry/opentelemetry-go/blob/29bdfd20e07a156f22a9c9148066aae6527f8219/exporters/otlp/otlptrace/otlptracegrpc/internal/envconfig/envconfig.go#L166-L170 The...

This is not necessary, but may be good for maintaining backward compatiblity. Should we do the same for `Record`, `KeyValue`, `Value` in `go.opentelemetry.io/otel/log`? _Originally posted by @pellared in https://github.com/open-telemetry/opentelemetry-go/pull/5693#discussion_r1708653552_

sdk/log: Add NoopProcessor

1

Blocked by: - https://github.com/open-telemetry/opentelemetry-specification/pull/4067 Fixes https://github.com/open-telemetry/opentelemetry-go/issues/5580

Add no-op processor

1

Blocked by: - https://github.com/open-telemetry/opentelemetry-specification/pull/4067 Here is another usage of an no-op processor in a processor implementation. I think we can think about adding it the the SDK as it can...

Add guidance on pinning GitHub Actions and container images

7

## Why A bad actor can force push a tag so that GitHub Action to do some malicious actions. A bad actor can push a malicious container image under the...

Flaky test: `IntegrationTests.DotNetCliTests.WorkFlow`

4

https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/actions/runs/10296118859/job/28497283365 ``` Error: [xUnit.net 00:10:33.55] IntegrationTests.DotNetCliTests.WorkFlow [FAIL] 05:19:30 [ERR] [xUnit.net 00:10:33.55] IntegrationTests.DotNetCliTests.WorkFlow [FAIL] 05:19:30 [DBG] [xUnit.net 00:10:33.55] IntegrationTests: --- FAIL: IntegrationTests.DotNetCliTests.WorkFlow() (25.30s) 05:19:30 [DBG] [xUnit.net 00:10:33.56] IntegrationTests: === RUN IntegrationTests.QuartzTests.SubmitsTraces(3.10.0)...

With several log bridges already implemented we can provide guidelines similar to https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/instrumentation/README.md on adding and designing new ones. However, at this point of time, it does not look important...