Audit for 1.14.0 spec compliance

[ahayworth]

Spec release 1.14.0 is available:

• Release notes
• Diff v1.13.0...v1.14.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.14.0 labels, and add them to the Spec Compliance project.

[ahayworth]

Traces

No changes.

Context

No changes.

Metrics

Nothing metrics related in this repo.

Logs

Logs?! What logs? 🙃

Resource

Nothing applicable.

Semantic Conventions

• The following would get pulled in when we update the semconv gem to 1.14
  • Add process.context_switches, and process.open_file_descriptors, to the metrics semantic conventions (Add additional process metrics to the metrics semantic conventions opentelemetry-specification#2706)
  • Add exceptions to the logs semantic conventions ([Logs] Add semantic conventions for writing exceptions opentelemetry-specification#2819)
  • Update http metrics to use http.route instead of http.target for servers, drop http.url for clients (Fix inconsistent metric usage of http.target opentelemetry-specification#2818).
• Make context propagation requirements explicit for messaging semantic conventions (Make messaging context propagation requirements explicit opentelemetry-specification#2750).
  • We do have instrumentation gems that deal with messaging, so this may be a substantial update.

Compatibility

No changes.

OpenTelemetry Protocol

• Add user agent to OTLP exporter specification (add user agent to OTLP exporter spec opentelemetry-specification#2684)
  • ✅ No exporters here, look elsewhere!
• Prohibit usage of enum value name strings in OTLP/JSON (Prohibit usage of enum value name strings in OTLP/JSON opentelemetry-specification#2758)
  • ✅ We don't implement OTLP/JSON
• Clarify that unknown fields must be ignored when receiving OTLP/JSON (Clarify that unknown fields must be ignored when receiving OTLP/JSON opentelemetry-specification#2816)
  • ✅ We don't implement OTLP/JSON
• Add OTLP exporter user agent to the spec compliance matrix (Update compliance matrix to reflect the OTLP user agent spec opentelemetry-specification#2842).
  • ✅ No exporters here, look elsewhere!

SDK Configuration

• Add the OTEL_SDK_DISABLED environment variable to the SDK configuration. (Add OTEL_SDK_DISABLED env var to disable opentelemetry SDK. opentelemetry-specification#2679)
  • ✅ No SDK configuration happening here, I think.
• Add the definition of a Boolean environment variable (Definition of boolean environment variables on the SDK opentelemetry-specification#2755).
  • Unsure if we need to do anything in this repo for this change (I doubt it).

Telemetry Schemas

No changes.

Common

No changes.

[github-actions]

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