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!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...