0.51.0
Added
- Semantic Logger trace correlation injection (#1566)
- New and improved Lograge trace correlation injection (#1555)
- Profiler: Start profiler on
ddtrace/auto_instrument
- CI-App: Add runtime and OS information (#1587)
- CI-App: Read metadata from local git repository (#1561)
Changed
-
Rename
Datadog::Runtime
toDatadog::Core::Environment
(#1570)As we prepare the
Datadog
Ruby namespace to better accommodate new products, we are moving a few internal modules to a different location to avoid conflicts.None of the affected files are exposed publicly in our documentation, and they are only expected to be used internally and may change at any time, even between patch releases.
- The following modules have been moved:
Datadog::Runtime::Cgroup -> Datadog::Core::Environment::Cgroup Datadog::Runtime::ClassCount -> Datadog::Core::Environment::ClassCount Datadog::Runtime::Container -> Datadog::Core::Environment::Container Datadog::Runtime::GC -> Datadog::Core::Environment::GC Datadog::Runtime::Identity -> Datadog::Core::Environment::Identity Datadog::Runtime::ObjectSpace -> Datadog::Core::Environment::ObjectSpace Datadog::Runtime::Socket -> Datadog::Core::Environment::Socket Datadog::Runtime::ThreadCount -> Datadog::Core::Environment::ThreadCount
- Most constants from
Datadog::Ext::Runtime
have been moved to a new module:Datadog::Core::Environment::Ext
.
-
Skip CPU time instrumentation if logging gem is detected (#1557)
Fixed
-
Initialize
dogstatsd-ruby
in single threaded mode (#1576)This should alleviate any existing issues with
dogstatsd-ruby
resource leaks. -
Do not use configured
dogstatsd-ruby
instance when it's an incompatible version (#1560) -
Ensure tags with special Datadog processing are consistently serialized (#1556)
-
Profiler: NameError during initialization (#1552)
Refactored
Read the full changeset and the release milestone.