opentelemetry-specification

opentelemetry-specification copied to clipboard

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

pellared

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

pellared

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

pellared

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

pellared

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

pellared

Clarify environment variable substitution is not recursive

4

Fixes #3894 ## Changes In the SDK file configuration, clarify environment variable substitution is not recursive. For non-trivial changes, follow the [change proposal process](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CONTRIBUTING.md#proposing-a-change). * [X] Related issues #3894 *...

marcalff

Mark metric overflow attribute section stable

2

Fixes #3904 ## Changes - Mark the [Overflow attribute](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#overflow-attribute) section under Cardinality limits as **Stable**. * [x] Related issues # * [ ] Related [OTEP(s)](https://github.com/open-telemetry/oteps) # * [ ] Links...

utpilla

Env var resource configuration should be RECOMMENDED and not optional

3

**What are you trying to achieve?** I'd like to be able to configure common **OTel resource attributes** via environment variables in the same way across different languages. Currently env var...

lmolkova

It is often not possible to send the same log data to multiple backends. This seems undesirable and unnecessary. Ultimately, I propose a new field on the log data model....

djaglowski

Clarification on `SeverityText` Usage Relative to Recommended Short Names

2

Hello OpenTelemetry team, I'm seeking guidance on several aspects of `SeverityText` and `SeverityNumber` as described in the OpenTelemetry logging specifications, particularly regarding the implementation and use of recommended short names....

10xLaCroixDrinker