Releases: DataDog/dd-trace-rb
0.23.2
0.23.1
0.23.0
0.22.0
In this release we are adding initial support for the beta Runtime metrics collection feature.
Changed
- Add warning log if an integration is incompatible (#722) (@ericmustin)
Added
- Initial beta support for Runtime metrics collection (#677)
Read the full changeset and the release milestone.
0.21.2
0.21.1
0.21.0
Added
Fixed
- Distributed traces with IDs in 2^64 range being dropped (#719)
- Custom logger level forced to warning (#681, #721) (@blaines, @ericmustin)
Refactored
- Global configuration for tracing into configuration API (#714)
Read the full changeset and the release milestone.
0.20.0
This release will log deprecation warnings for any usage of Datadog::Pin
.
These changes are backwards compatible, but all integration configuration should be moved away from Pin
and to the configuration API instead.
Added
- Propagate synthetics origin header (#699)
Changed
- Enable distributed tracing by default (#701)
Fixed
- Fix Rack http_server.queue spans missing from distributed traces (#709)
Refactored
- Refactor MongoDB to use instrumentation module (#704)
- Refactor HTTP to use instrumentation module (#703)
- Deprecate GRPC global pin in favor of configuration API (#702)
- Deprecate Grape pin in favor of configuration API (#700)
- Deprecate Faraday pin in favor of configuration API (#696)
- Deprecate Dalli pin in favor of configuration API (#693)
Read the full changeset and the release milestone.
0.19.1
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.