Telemetry.sdk.* attributes not automatically added to resource

[thompson-tomo]

As per the spec

The SDK MUST provide access to a Resource with at least the attributes listed at Semantic Attributes with SDK-provided Default Value.

When you look at that https://opentelemetry.io/docs/specs/semconv/resource/#semantic-attributes-with-sdk-provided-default-value you get:

• service.name
• telemetry.sdk group

Which expands to

• service.name
• telemetry.sdk.name
• telemetry.sdk.language
• telemetry.sdk.version

Originally posted by @thompson-tomo in open-telemetry/opentelemetry-ruby-contrib#1384 (comment)

[robbkidd]

The SDK does provide these by default.

irb(main):001> require 'opentelemetry/sdk'
=> true
irb(main):002> OpenTelemetry::SDK.configure
W, [2026-04-24T19:39:29.132923 #1]  WARN -- : The otlp exporter cannot be configured - please add opentelemetry-exporter-otlp to your Gemfile, spans will not be exported
=> nil

irb(main):003> OpenTelemetry.tracer_provider.resource
=> 
#<OpenTelemetry::SDK::Resources::Resource:0x0000ffff87214d28
 @attribute_enumerator=#<Enumerator: ...>,
 @attributes=
  {"service.name"=>"unknown_service",
   "process.pid"=>1,
   "process.command"=>"irb",
   "process.runtime.name"=>"ruby",
   "process.runtime.version"=>"3.3.6",
   "process.runtime.description"=>"ruby 3.3.6 (2024-11-05 revision 75015d4c1f) [aarch64-linux-musl]",
   "telemetry.sdk.name"=>"opentelemetry",
   "telemetry.sdk.language"=>"ruby",
   "telemetry.sdk.version"=>"1.11.0"}>

I recommend closing this issue. If the use case born out by attempts at a more magical auto-initializing gem show places where configuring the SDK is troublesome, we'll need more specific requests about what the behavior ought to be.