Audit for 1.13.0 spec compliance

[ahayworth]

Spec release 1.13.0 is available:

• Release notes
• Diff v1.12.0...v1.13.0

The release should be audited for issues pertinent to opentelemetry-ruby-contrib, and issues created for any outstanding spec compliance work. Make sure to tag those issues with the spec-compliance and spec-compliance/v1.13.0 labels, and add them to the Spec Compliance project.

[ahayworth]

Traces

Nothing relevant

Metrics

Nothing metrics related in this repo.

Logs

Logs? What logs? 🙃

Resource

• [x] Update the version of the W3C Baggage specification used for OTEL_RESOURCE_ATTRIBUTES (https://github.com/open-telemetry/opentelemetry-specification/pull/2670)
  • Tracked in main repo: open-telemetry/opentelemetry-ruby#1361

Semantic Conventions

• [ ] Add process.parent_pid attribute for use in reporting parent process id (PID) (https://github.com/open-telemetry/opentelemetry-specification/pull/2691)
• [ ] Clarify when "count" is used instead of pluralization (https://github.com/open-telemetry/opentelemetry-specification/pull/2613)
• [ ] Adopt attribute requirement levels in semantic conventions (https://github.com/open-telemetry/opentelemetry-specification/pull/2594)
  • Since attribute requirement levels were just adopted, these should come along "for free" and don't need separate auditing (I think).
  • Change cloudevents.event_spec_version and cloudevents.event_type level from required to recommended (https://github.com/open-telemetry/opentelemetry-specification/pull/2618)
  • Change faas.document.time and faas.time level from required to recommended (https://github.com/open-telemetry/opentelemetry-specification/pull/2627)
• [ ] BREAKING: rename net.peer.ip to net.sock.peer.addr, net.host.ip to net.sock.host.addr, net.peer.name to net.sock.peer.name for socket-level instrumentation.
  • This change should get pulled in with the update to semconv, but we should audit to ensure that we update any calling code which might be referencing it.
  • We reference this manually in the pg instrumentation, I believe.

OpenTelemetry Protocol

Nothing relevant.

SDK Configuration

Nothing relevant.

Telemetry Schemas

Nothing relevant.

Common

• [ ] Introduce Instrumentation Scope Attributes (https://github.com/open-telemetry/opentelemetry-specification/pull/2579)
  • [ ] Define Instrumentation Scope Attributes as non identifiers (https://github.com/open-telemetry/opentelemetry-specification/pull/2789)

[github-actions[bot]]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.