Splunk Dev

Ruby SDK on Ruby 2.0?

lloesche
Engager

Ruby 2 is over half a year old by now. Yet the splunk SDK for ruby 1.0.2 fails with the message:

/opt/local/lib/ruby2.0/gems/2.0.0/gems/splunk-sdk-ruby-1.0.2/lib/splunk-sdk-ruby/context.rb:401:in `request_by_url': uninitialized constant Splunk::Context::OpenSSL (NameError)
from /opt/local/lib/ruby2.0/gems/2.0.0/gems/splunk-sdk-ruby-1.0.2/lib/splunk-sdk-ruby/context.rb:314:in `request'
from /opt/local/lib/ruby2.0/gems/2.0.0/gems/splunk-sdk-ruby-1.0.2/lib/splunk-sdk-ruby/context.rb:196:in `login'
from /opt/local/lib/ruby2.0/gems/2.0.0/gems/splunk-sdk-ruby-1.0.2/lib/splunk-sdk-ruby/service.rb:82:in `connect'
from ./3_blocking_searches.rb:31:in `<main>'

On 1.9.3 (and only 1.9.3 - 1.8.7 fails too) it works out of the box. We're currently working around the problem by accessing the REST API directly. Are there any plans to make the SDK ruby2 compatible or is the project dead?

Tags (2)

e7sal
New Member

We have the same problem.

Any information to help us would be extremely helpful. We are considering another logging platform as we don't want to have to rollback to ruby 1.9.3/

Thanks

0 Karma
Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...