Robert Pająk

[file configuration] Clarify what should happen for invalid environment variable substitution

3

**What are you trying to achieve?** From: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/file-configuration.md#environment-variable-substitution > For example, `${API_KEY}` is valid, while `${1API_KEY}` and `${API_$KEY}` are invalid. I think saying "invalid" does not make it clear how...

[file configuration] Escaping environment variable substitution

6

**What are you trying to achieve?** Reference: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/file-configuration.md#environment-variable-substitution I would like to set a string value to `${NOT_ENV_VAR}` and make sure it is not escaped. **Additional context.** I think that...

Change map to key-value pair collection in Logs Data Model

1

## Why Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/3931 ### Performance Checking for duplicates introduces performance overhead which can be undesirable for systems where logging should be high-performant. Changing the data model definition would allow...

Define case sensitivity of map<string, any> keys in Logs Data Model

7

Per https://github.com/open-telemetry/opentelemetry-specification/pull/3853#discussion_r1496176569 ## Changes Add clarifications to `map` taken from https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/common and make the description more normative. The spec is stable, but I think that it is rather a clarification...

Clarify that ReadableLogRecord and ReadWriteLogRecord can be represented using a single type

6

Currently, the [Logs SDK specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/sdk.md#additional-logrecord-interfaces) says: > In addition to the [definition for LogRecord](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#log-and-event-record-definition), the following LogRecord-like interfaces are defined in the SDK: > ### ReadableLogRecord > [...] > Note:...

Fix what can be modified via ReadWriteLogRecord

1

Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/3902 ## Changes Fix what can be modified via `ReadWriteLogRecord`.

Refine description of Instrumentation Scope for Logs

1

Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/3841 ## Changes - Update "Instrumentation Scope" term in glossary. - Update "Attribute Collections" (in common definitions) to include instrumentation scope attributes. - Change the instrumentation scope type definition...

Clarify what LogRecordProcessor is able to modify

2

**What are you trying to achieve?** I want to model `LogRecordProcessor` for Go SDK (https://github.com/open-telemetry/opentelemetry-go/issues/4896). Currently this is what [the spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/sdk.md#readwritelogrecord) says about `ReadWriteLogRecord` (the `OnEmit` argument): > A function...

From https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/bridge-api.md#get-a-logger: > - `attributes` (optional): Specifies the instrumentation scope attributes to associate with emitted telemetry. This API MUST be structured to accept a variable number of attributes, including none....

otelmemcache deprecation

1

I am creating this issue to inform you that we (OpenTelemetry contributors) are planning to deprecate https://pkg.go.dev/go.opentelemetry.io/contrib/instrumentation/github.com/bradfitz/gomemcache/memcache/otelmemcache. You can consider copying the OpenTelemetry instrumentation to this repository or organization. You...