0.19.0

This release adds a few new features for users who use Datadog's logging, trace search & analytics feature.

Easy correlation between logs and tracing

The tracer now has active_correlation method which can return the trace ID and span ID of the active trace. This can be used to correlate application logs with traces.

Rails users can implement this with:

Rails.application.configure do
  config.log_tags = [proc { Datadog.tracer.active_correlation.to_s }]
end

For more details, and other implementations for Ruby applications, check out the documentation.

Opt-in support for adding additional instrumentation to trace search & analytics

Some integrations now can be configured with a event_sample_rate option to enable sampling their spans for trace search for analytics, including:

• Delayed Job
• Racecar
• Rack
• Rake
• Resque
• Shoryuken
• Sidekiq
• Sucker Punch

For example, to enable for Rack, add the following to your configuration file:

Datadog.configure do |c|
  c.use :rack, event_sample_rate: 1.0
end

To learn more about trace search and analytics, check out our blog post and documentation. For more details on how to implement, check out the tracer documentation.

Added

• Tracer#active_correlation for adding correlation IDs to logs. (#660, #664, #673)
• Opt-in support for event_sample_rate tag for some integrations. (#665, #666)

Changed

• Priority sampling enabled by default. (#654)

Read the full changeset and the release milestone.