Skip to content

Clarify protocol defaults on specification#4585

Merged
carlosalberto merged 5 commits intoopen-telemetry:mainfrom
gustavo-vargas-leon:clarify-protocol-defaults
Jul 23, 2025
Merged

Clarify protocol defaults on specification#4585
carlosalberto merged 5 commits intoopen-telemetry:mainfrom
gustavo-vargas-leon:clarify-protocol-defaults

Conversation

@gustavo-vargas-leon
Copy link
Contributor

@gustavo-vargas-leon gustavo-vargas-leon commented Jul 10, 2025

Fixes #4582

Clarify the default OTLP protocol, it's not always http/protobuf.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Jul 10, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: gustavo-vargas-leon / name: Gustavo Vargas (43a1f56)
  • ✅ login: carlosalberto / name: Carlos Alberto Cortez (ec1186a)
  • ✅ login: cijothomas / name: Cijo Thomas (29404b2)
  • ✅ login: pellared / name: Robert Pająk (dd41ae1, 0509391)

@pellared pellared added spec:protocol Related to the specification/protocol directory clarification clarify ambiguity in specification labels Jul 11, 2025
@pellared
Copy link
Member

pellared commented Jul 11, 2025

@gustavo-vargas-leon, I modified the PR description. I hope you are fine with it. Thanks for your contribution!

@chadxz
Copy link

chadxz commented Jul 12, 2025

Can someone help us with the CI check failure? Looks like it flaked?

@chadxz
Copy link

chadxz commented Jul 15, 2025

Looks like it’s all green ✅ :shipit:

@carlosalberto carlosalberto added this pull request to the merge queue Jul 23, 2025
Merged via the queue into open-telemetry:main with commit 09a2718 Jul 23, 2025
10 of 11 checks passed
@chadxz
Copy link

chadxz commented Jul 23, 2025

Congratulations @gustavo-vargas-leon on your first open source contribution! 😍

@carlosalberto carlosalberto mentioned this pull request Aug 11, 2025
github-merge-queue bot pushed a commit that referenced this pull request Aug 13, 2025
August 2025 release.

### Logs

- Improve concurrency safety description of `LogRecordProcessor.OnEmit`.

([#4578](#4578))
- Clarify that `SeverityNumber` values are used when comparing
severities.

([#4552](#4552))

### Entities

- Mention entity references in the stability guarantees.

([#4593](#4593))

### OpenTelemetry Protocol

- Clarify protocol defaults on specification.

([#4585](#4585))

### Compatibility

- Flexibilie escaping of characters that are discouraged by Prometheus
Conventions
  in Prometheus exporters.

([#4533](#4533))
- Flexibilize addition of unit/type related suffixes in Prometheus
exporters.

([#4533](#4533))
- Define the configuration option "Translation Strategies" for
Prometheus exporters.

([#4533](#4533))
- Define conversion of Prometheus native histograms to OpenTelemetry
exponential histograms.

([#4561](#4561))
- Clarify what to do when scope attribute conflicts with name, version
and schema URL.

([#4599](#4599))

### SDK Configuration

- Enum values provided via environment variables SHOULD be interpreted
in a case-insensitive manner.

([#4576](#4576))

Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clarification clarify ambiguity in specification spec:protocol Related to the specification/protocol directory

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OpenTelemetry Protocol Exporter gives no warning about protocol default possibly being different across SDKs

6 participants