ddtrace 0.50.0 → 0.51.1

data/CHANGELOG.md

@@ -2,6 +2,66 @@
 
 ## [Unreleased]
 
+## [0.51.1] - 2021-07-13
+
+Release notes: https://github.com/DataDog/dd-trace-rb/releases/tag/v0.51.1
+
+Git diff: https://github.com/DataDog/dd-trace-rb/compare/v0.51.0...v0.51.1
+
+### Fixed
+
+- AWS-SDK instrumentation without `aws-sdk-s3` ([#1592][])
+
+## [0.51.0] - 2021-07-12
+
+Release notes: https://github.com/DataDog/dd-trace-rb/releases/tag/v0.51.0
+
+Git diff: https://github.com/DataDog/dd-trace-rb/compare/v0.50.0...v0.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` to `Datadog::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:
+  ```ruby
+  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
+- Improvements to test suite & CI ([#1586][])
+- Improvements to documentation ([#1397][])
+
 ## [0.50.0] - 2021-06-07
 
 Release notes: https://github.com/DataDog/dd-trace-rb/releases/tag/v0.50.0
@@ -1713,6 +1773,8 @@ Release notes: https://github.com/DataDog/dd-trace-rb/releases/tag/v0.3.1
 Git diff: https://github.com/DataDog/dd-trace-rb/compare/v0.3.0...v0.3.1
 
 [Unreleased]: https://github.com/DataDog/dd-trace-rb/compare/v0.48.0...master
+[0.51.1]: https://github.com/DataDog/dd-trace-rb/compare/v0.51.0...v0.51.1
+[0.51.0]: https://github.com/DataDog/dd-trace-rb/compare/v0.50.0...v0.51.0
 [0.48.0]: https://github.com/DataDog/dd-trace-rb/compare/v0.47.0...v0.48.0
 [0.47.0]: https://github.com/DataDog/dd-trace-rb/compare/v0.46.0...v0.47.0
 [0.46.0]: https://github.com/DataDog/dd-trace-rb/compare/v0.45.0...v0.46.0
@@ -2359,6 +2421,7 @@ Git diff: https://github.com/DataDog/dd-trace-rb/compare/v0.3.0...v0.3.1
 [#1393]: https://github.com/DataDog/dd-trace-rb/issues/1393
 [#1394]: https://github.com/DataDog/dd-trace-rb/issues/1394
 [#1396]: https://github.com/DataDog/dd-trace-rb/issues/1396
+[#1397]: https://github.com/DataDog/dd-trace-rb/issues/1397
 [#1398]: https://github.com/DataDog/dd-trace-rb/issues/1398
 [#1399]: https://github.com/DataDog/dd-trace-rb/issues/1399
 [#1400]: https://github.com/DataDog/dd-trace-rb/issues/1400
@@ -2419,6 +2482,18 @@ Git diff: https://github.com/DataDog/dd-trace-rb/compare/v0.3.0...v0.3.1
 [#1537]: https://github.com/DataDog/dd-trace-rb/issues/1537
 [#1543]: https://github.com/DataDog/dd-trace-rb/issues/1543
 [#1544]: https://github.com/DataDog/dd-trace-rb/issues/1544
+[#1552]: https://github.com/DataDog/dd-trace-rb/issues/1552
+[#1555]: https://github.com/DataDog/dd-trace-rb/issues/1555
+[#1556]: https://github.com/DataDog/dd-trace-rb/issues/1556
+[#1557]: https://github.com/DataDog/dd-trace-rb/issues/1557
+[#1560]: https://github.com/DataDog/dd-trace-rb/issues/1560
+[#1561]: https://github.com/DataDog/dd-trace-rb/issues/1561
+[#1566]: https://github.com/DataDog/dd-trace-rb/issues/1566
+[#1570]: https://github.com/DataDog/dd-trace-rb/issues/1570
+[#1576]: https://github.com/DataDog/dd-trace-rb/issues/1576
+[#1586]: https://github.com/DataDog/dd-trace-rb/issues/1586
+[#1587]: https://github.com/DataDog/dd-trace-rb/issues/1587
+[#1592]: https://github.com/DataDog/dd-trace-rb/issues/1592
 [@AdrianLC]: https://github.com/AdrianLC
 [@Azure7111]: https://github.com/Azure7111
 [@BabyGroot]: https://github.com/BabyGroot

data/Gemfile

@@ -15,6 +15,7 @@ gem 'memory_profiler', '~> 0.9'
 gem 'minitest', '= 5.10.1'
 gem 'minitest-around', '0.5.0'
 gem 'minitest-stub_any_instance', '1.0.2'
+gem 'os', '~> 1.1'
 gem 'pimpmychangelog', '>= 0.1.2'
 gem 'pry'
 if RUBY_PLATFORM != 'java'
@@ -25,12 +26,12 @@ if RUBY_PLATFORM != 'java'
 else
   gem 'pry-debugger-jruby'
 end
-gem 'rake', '>= 10.5'
+gem 'rake', '>= 10.5', '< 13.0.4' # Locking rake until https://github.com/thoughtbot/appraisal/pull/184 is released
 gem 'redcarpet', '~> 3.4' if RUBY_PLATFORM != 'java'
 gem 'rspec', '~> 3.10'
 gem 'rspec-collection_matchers', '~> 1.1'
 gem 'rspec_junit_formatter', '>= 0.4.1'
-gem 'rspec_n', '~> 1.3' if RUBY_VERSION >= '2.3.0'
+gem 'rspec_n', '~> 1.3' if RUBY_VERSION >= '2.4.0'
 gem 'ruby-prof', '~> 1.4' if RUBY_PLATFORM != 'java' && RUBY_VERSION >= '2.4.0'
 if RUBY_VERSION >= '2.5.0'
   # Merging branch coverage results does not work for old, unsupported rubies.
@@ -58,7 +59,9 @@ end
 
 # Optional extensions
 # TODO: Move this to Appraisals?
-gem 'dogstatsd-ruby', '>= 3.3.0'
+# dogstatsd v5, but lower than 5.2, has possible memory leak with ddtrace.
+# @see https://github.com/DataDog/dogstatsd-ruby/issues/182
+gem 'dogstatsd-ruby', '>= 3.3.0', '!= 5.0.0', '!= 5.0.1', '!= 5.1.0'
 gem 'opentracing', '>= 0.4.1'
 
 # Profiler optional dependencies

data/Rakefile

@@ -39,7 +39,8 @@ namespace :spec do
 
   RSpec::Core::RakeTask.new(:rails) do |t, args|
     t.pattern = 'spec/ddtrace/contrib/rails/**/*_spec.rb'
-    t.exclude_pattern = 'spec/ddtrace/contrib/rails/**/*{active_job,disable_env,redis_cache,auto_instrument}*_spec.rb'
+    t.exclude_pattern = 'spec/ddtrace/contrib/rails/**/*{active_job,disable_env,redis_cache,auto_instrument,'\
+                        'semantic_logger}*_spec.rb'
     t.rspec_opts = args.to_a.join(' ')
   end
 
@@ -68,6 +69,14 @@ namespace :spec do
     t.rspec_opts = args.to_a.join(' ')
   end
 
+  # rails_semantic_logger is the dog at the dog park that doesnt play nicely with other
+  # logging gems, aka it tries to bite/monkeypatch them, so we have to put it in its own appraisal and rake task
+  # in order to isolate its effects for rails logs auto injection
+  RSpec::Core::RakeTask.new(:railssemanticlogger) do |t, args|
+    t.pattern = 'spec/ddtrace/contrib/rails/**/*rails_semantic_logger*_spec.rb'
+    t.rspec_opts = args.to_a.join(' ')
+  end
+
   RSpec::Core::RakeTask.new(:contrib) do |t, args|
     contrib_paths = [
       'analytics',
@@ -111,6 +120,7 @@ namespace :spec do
     :httpclient,
     :httprb,
     :kafka,
+    :lograge,
     :mongodb,
     :mysql2,
     :presto,
@@ -123,6 +133,7 @@ namespace :spec do
     :resque,
     :rest_client,
     :rspec,
+    :semantic_logger,
     :sequel,
     :shoryuken,
     :sidekiq,
@@ -259,6 +270,7 @@ task :ci do
     declare 'bundle exec appraisal contrib-old rake spec:resque'
     declare 'bundle exec appraisal contrib-old rake spec:rest_client'
     declare 'bundle exec appraisal contrib-old rake spec:rspec'
+    declare 'bundle exec appraisal contrib-old rake spec:semantic_logger'
     declare 'bundle exec appraisal contrib-old rake spec:sequel'
     declare 'bundle exec appraisal contrib-old rake spec:sidekiq'
     declare 'bundle exec appraisal contrib-old rake spec:sinatra'
@@ -278,6 +290,7 @@ task :ci do
     declare 'bundle exec appraisal rails4-postgres-redis rake spec:railsredis'
     declare 'bundle exec appraisal rails4-postgres rake spec:railsdisableenv'
     declare 'bundle exec appraisal rails4-postgres rake spec:railsautoinstrument'
+    declare 'bundle exec appraisal rails4-semantic-logger rake spec:railssemanticlogger'
     # Rails specs
     declare 'bundle exec appraisal rails30-postgres rake spec:rails'
     declare 'bundle exec appraisal rails32-mysql2 rake spec:rails'
@@ -320,6 +333,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:http'
     declare 'bundle exec appraisal contrib rake spec:httpclient'
     declare 'bundle exec appraisal contrib rake spec:httprb'
+    declare 'bundle exec appraisal contrib rake spec:lograge'
     declare 'bundle exec appraisal contrib rake spec:kafka'
     declare 'bundle exec appraisal contrib rake spec:mongodb'
     declare 'bundle exec appraisal contrib rake spec:mysql2'
@@ -333,6 +347,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:resque'
     declare 'bundle exec appraisal contrib rake spec:rest_client'
     declare 'bundle exec appraisal contrib rake spec:rspec'
+    declare 'bundle exec appraisal contrib rake spec:semantic_logger'
     declare 'bundle exec appraisal contrib rake spec:sequel'
     declare 'bundle exec appraisal contrib rake spec:shoryuken'
     declare 'bundle exec appraisal contrib rake spec:sidekiq'
@@ -362,6 +377,8 @@ task :ci do
     declare 'bundle exec appraisal rails5-postgres-sidekiq rake spec:railsactivejob'
     declare 'bundle exec appraisal rails5-postgres rake spec:railsdisableenv'
     declare 'bundle exec appraisal rails5-postgres rake spec:railsautoinstrument'
+    declare 'bundle exec appraisal rails4-semantic-logger rake spec:railssemanticlogger'
+    declare 'bundle exec appraisal rails5-semantic-logger rake spec:railssemanticlogger'
     # Rails specs
     declare 'bundle exec appraisal rails30-postgres rake spec:rails'
     declare 'bundle exec appraisal rails32-mysql2 rake spec:rails'
@@ -401,6 +418,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:http'
     declare 'bundle exec appraisal contrib rake spec:httpclient'
     declare 'bundle exec appraisal contrib rake spec:httprb'
+    declare 'bundle exec appraisal contrib rake spec:lograge'
     declare 'bundle exec appraisal contrib rake spec:kafka'
     declare 'bundle exec appraisal contrib rake spec:mongodb'
     declare 'bundle exec appraisal contrib rake spec:mysql2'
@@ -413,6 +431,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:resque'
     declare 'bundle exec appraisal contrib rake spec:rest_client'
     declare 'bundle exec appraisal contrib rake spec:rspec'
+    declare 'bundle exec appraisal contrib rake spec:semantic_logger'
     declare 'bundle exec appraisal contrib rake spec:sequel'
     declare 'bundle exec appraisal contrib rake spec:shoryuken'
     declare 'bundle exec appraisal contrib rake spec:sidekiq'
@@ -444,6 +463,8 @@ task :ci do
     declare 'bundle exec appraisal rails5-postgres-sidekiq rake spec:railsactivejob'
     declare 'bundle exec appraisal rails5-postgres rake spec:railsdisableenv'
     declare 'bundle exec appraisal rails5-postgres rake spec:railsautoinstrument'
+    declare 'bundle exec appraisal rails4-semantic-logger rake spec:railssemanticlogger'
+    declare 'bundle exec appraisal rails5-semantic-logger rake spec:railssemanticlogger'
     # Rails specs
     declare 'bundle exec appraisal rails30-postgres rake spec:rails'
     declare 'bundle exec appraisal rails32-mysql2 rake spec:rails'
@@ -488,6 +509,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:http'
     declare 'bundle exec appraisal contrib rake spec:httpclient'
     declare 'bundle exec appraisal contrib rake spec:httprb'
+    declare 'bundle exec appraisal contrib rake spec:lograge'
     declare 'bundle exec appraisal contrib rake spec:kafka'
     declare 'bundle exec appraisal contrib rake spec:mongodb'
     declare 'bundle exec appraisal contrib rake spec:mysql2'
@@ -500,6 +522,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:resque'
     declare 'bundle exec appraisal contrib rake spec:rest_client'
     declare 'bundle exec appraisal contrib rake spec:rspec'
+    declare 'bundle exec appraisal contrib rake spec:semantic_logger'
     declare 'bundle exec appraisal contrib rake spec:sequel'
     declare 'bundle exec appraisal contrib rake spec:shoryuken'
     declare 'bundle exec appraisal contrib rake spec:sidekiq'
@@ -518,6 +541,7 @@ task :ci do
     declare 'bundle exec appraisal rails5-postgres-sidekiq rake spec:railsactivejob'
     declare 'bundle exec appraisal rails5-postgres rake spec:railsdisableenv'
     declare 'bundle exec appraisal rails5-postgres rake spec:railsautoinstrument'
+    declare 'bundle exec appraisal rails5-semantic-logger rake spec:railssemanticlogger'
     # Rails specs
     declare 'bundle exec appraisal rails5-mysql2 rake spec:rails'
     declare 'bundle exec appraisal rails5-postgres rake spec:rails'
@@ -561,6 +585,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:http'
     declare 'bundle exec appraisal contrib rake spec:httpclient'
     declare 'bundle exec appraisal contrib rake spec:httprb'
+    declare 'bundle exec appraisal contrib rake spec:lograge'
     declare 'bundle exec appraisal contrib rake spec:kafka'
     declare 'bundle exec appraisal contrib rake spec:mongodb'
     declare 'bundle exec appraisal contrib rake spec:mysql2' if RUBY_PLATFORM != 'java' # built-in jdbc is used instead
@@ -574,6 +599,7 @@ task :ci do
     declare 'bundle exec appraisal contrib rake spec:resque'
     declare 'bundle exec appraisal contrib rake spec:rest_client'
     declare 'bundle exec appraisal contrib rake spec:rspec'
+    declare 'bundle exec appraisal contrib rake spec:semantic_logger'
     declare 'bundle exec appraisal contrib rake spec:sequel'
     declare 'bundle exec appraisal contrib rake spec:shoryuken'
     declare 'bundle exec appraisal contrib rake spec:sidekiq'
@@ -599,6 +625,9 @@ task :ci do
     declare 'bundle exec appraisal rails6-postgres-sidekiq rake spec:railsactivejob'
     declare 'bundle exec appraisal rails6-postgres rake spec:railsdisableenv'
     declare 'bundle exec appraisal rails6-postgres rake spec:railsautoinstrument'
+    declare 'bundle exec appraisal rails5-semantic-logger rake spec:railssemanticlogger'
+    declare 'bundle exec appraisal rails6-semantic-logger rake spec:railssemanticlogger'
+    declare 'bundle exec appraisal rails61-semantic-logger rake spec:railssemanticlogger'
     # Rails specs
     declare 'bundle exec appraisal rails5-mysql2 rake spec:action_cable'
     declare 'bundle exec appraisal rails5-mysql2 rake spec:rails'
@@ -657,6 +686,7 @@ task :ci do
       declare 'bundle exec appraisal contrib rake spec:http'
       declare 'bundle exec appraisal contrib rake spec:httpclient'
       declare 'bundle exec appraisal contrib rake spec:httprb'
+      declare 'bundle exec appraisal contrib rake spec:lograge'
       declare 'bundle exec appraisal contrib rake spec:kafka'
       declare 'bundle exec appraisal contrib rake spec:mongodb'
       declare 'bundle exec appraisal contrib rake spec:mysql2'
@@ -670,6 +700,7 @@ task :ci do
       declare 'bundle exec appraisal contrib rake spec:resque'
       declare 'bundle exec appraisal contrib rake spec:rest_client'
       declare 'bundle exec appraisal contrib rake spec:rspec'
+      declare 'bundle exec appraisal contrib rake spec:semantic_logger'
       declare 'bundle exec appraisal contrib rake spec:sequel'
       declare 'bundle exec appraisal contrib rake spec:shoryuken'
       declare 'bundle exec appraisal contrib rake spec:sidekiq'
@@ -696,6 +727,9 @@ task :ci do
       declare 'bundle exec appraisal rails6-postgres-sidekiq rake spec:railsactivejob'
       declare 'bundle exec appraisal rails6-postgres rake spec:railsdisableenv'
       declare 'bundle exec appraisal rails6-postgres rake spec:railsautoinstrument'
+      declare 'bundle exec appraisal rails5-semantic-logger rake spec:railssemanticlogger'
+      declare 'bundle exec appraisal rails6-semantic-logger rake spec:railssemanticlogger'
+      declare 'bundle exec appraisal rails61-semantic-logger rake spec:railssemanticlogger'
       # Rails specs
       declare 'bundle exec appraisal rails5-mysql2 rake spec:action_cable'
       declare 'bundle exec appraisal rails5-mysql2 rake spec:rails'
@@ -755,6 +789,7 @@ task :ci do
       declare 'bundle exec appraisal contrib rake spec:http'
       declare 'bundle exec appraisal contrib rake spec:httpclient'
       declare 'bundle exec appraisal contrib rake spec:httprb'
+      declare 'bundle exec appraisal contrib rake spec:lograge'
       declare 'bundle exec appraisal contrib rake spec:kafka'
       declare 'bundle exec appraisal contrib rake spec:mongodb'
       declare 'bundle exec appraisal contrib rake spec:mysql2'
@@ -768,6 +803,7 @@ task :ci do
       declare 'bundle exec appraisal contrib rake spec:resque'
       declare 'bundle exec appraisal contrib rake spec:rest_client'
       declare 'bundle exec appraisal contrib rake spec:rspec'
+      declare 'bundle exec appraisal contrib rake spec:semantic_logger'
       declare 'bundle exec appraisal contrib rake spec:sequel'
       declare 'bundle exec appraisal contrib rake spec:shoryuken'
       declare 'bundle exec appraisal contrib rake spec:sidekiq'
@@ -794,6 +830,9 @@ task :ci do
       declare 'bundle exec appraisal rails6-postgres-sidekiq rake spec:railsactivejob'
       declare 'bundle exec appraisal rails6-postgres rake spec:railsdisableenv'
       declare 'bundle exec appraisal rails6-postgres rake spec:railsautoinstrument'
+      declare 'bundle exec appraisal rails5-semantic-logger rake spec:railssemanticlogger'
+      declare 'bundle exec appraisal rails6-semantic-logger rake spec:railssemanticlogger'
+      declare 'bundle exec appraisal rails61-semantic-logger rake spec:railssemanticlogger'
       # Rails specs
       declare 'bundle exec appraisal rails5-mysql2 rake spec:rails'
       declare 'bundle exec appraisal rails5-postgres rake spec:rails'
@@ -850,6 +889,8 @@ task :ci do
       declare 'bundle exec appraisal contrib rake spec:http'
       declare 'bundle exec appraisal contrib rake spec:httpclient'
       declare 'bundle exec appraisal contrib rake spec:httprb'
+      # lograge nested dependancy thor ~> 1.0 conflicts w/qless dependancy thor ~> 0.19.1
+      # declare 'bundle exec appraisal contrib rake spec:lograge'
       declare 'bundle exec appraisal contrib rake spec:kafka'
       declare 'bundle exec appraisal contrib rake spec:mongodb'
       declare 'bundle exec appraisal contrib rake spec:mysql2'
@@ -863,6 +904,7 @@ task :ci do
       declare 'bundle exec appraisal contrib rake spec:resque'
       declare 'bundle exec appraisal contrib rake spec:rest_client'
       declare 'bundle exec appraisal contrib rake spec:rspec'
+      declare 'bundle exec appraisal contrib rake spec:semantic_logger'
       declare 'bundle exec appraisal contrib rake spec:sequel'
       declare 'bundle exec appraisal contrib rake spec:shoryuken'
       declare 'bundle exec appraisal contrib rake spec:sidekiq'
@@ -880,6 +922,7 @@ task :ci do
       declare 'bundle exec appraisal rails61-postgres rake test:rails'
       declare 'bundle exec appraisal rails61-postgres-redis rake spec:railsredis'
       declare 'bundle exec appraisal rails61-postgres-sidekiq rake spec:railsactivejob'
+      declare 'bundle exec appraisal rails61-semantic-logger rake spec:railssemanticlogger'
 
       # explicitly test resque-2x compatability
       declare 'bundle exec appraisal resque2-redis3 rake spec:resque'
@@ -936,4 +979,4 @@ namespace :changelog do
   end
 end
 
-task default: :test
+task default: 'spec:main'

data/docker-compose.yml

@@ -2,7 +2,7 @@ version: '3.2'
 services:
   # MRI
   tracer-2.1:
-    image: palazzem/docker-library:ddtrace_rb_2_1_10
+    image: ivoanjo/docker-library:ddtrace_rb_2_1_10
     command: /bin/bash
     depends_on:
       - ddagent
@@ -32,7 +32,7 @@ services:
       - .:/app
       - bundle-2.1:/usr/local/bundle
   tracer-2.2:
-    image: palazzem/docker-library:ddtrace_rb_2_2_10
+    image: ivoanjo/docker-library:ddtrace_rb_2_2_10
     command: /bin/bash
     depends_on:
       - ddagent
@@ -62,7 +62,7 @@ services:
       - .:/app
       - bundle-2.2:/usr/local/bundle
   tracer-2.3:
-    image: palazzem/docker-library:ddtrace_rb_2_3_8
+    image: ivoanjo/docker-library:ddtrace_rb_2_3_8
     command: /bin/bash
     depends_on:
       - ddagent
@@ -92,7 +92,7 @@ services:
       - .:/app
       - bundle-2.3:/usr/local/bundle
   tracer-2.4:
-    image: palazzem/docker-library:ddtrace_rb_2_4_6
+    image: ivoanjo/docker-library:ddtrace_rb_2_4_10
     command: /bin/bash
     depends_on:
       - ddagent
@@ -122,7 +122,7 @@ services:
       - .:/app
       - bundle-2.4:/usr/local/bundle
   tracer-2.5:
-    image: marcotc/docker-library:ddtrace_rb_2_5_6
+    image: ivoanjo/docker-library:ddtrace_rb_2_5_9
     command: /bin/bash
     depends_on:
       - ddagent
@@ -152,7 +152,7 @@ services:
       - .:/app
       - bundle-2.5:/usr/local/bundle
   tracer-2.6:
-    image: marcotc/docker-library:ddtrace_rb_2_6_4
+    image: ivoanjo/docker-library:ddtrace_rb_2_6_7
     command: /bin/bash
     depends_on:
       - ddagent
@@ -182,7 +182,7 @@ services:
       - .:/app
       - bundle-2.6:/usr/local/bundle
   tracer-2.7:
-    image: marcotc/docker-library:ddtrace_rb_2_7_0
+    image: ivoanjo/docker-library:ddtrace_rb_2_7_3
     command: /bin/bash
     depends_on:
       - ddagent
@@ -212,7 +212,7 @@ services:
       - .:/app
       - bundle-2.7:/usr/local/bundle
   tracer-3.0:
-    image: marcotc/docker-library:ddtrace_rb_3.0.0
+    image: ivoanjo/docker-library:ddtrace_rb_3_0_1
     command: /bin/bash
     depends_on:
       - ddagent
@@ -240,7 +240,7 @@ services:
       - bundle-3.0:/usr/local/bundle
   # JRuby
   tracer-jruby-9.2.0.0:
-    image: marcotc/docker-library:ddtrace_rb_jruby_9_2_0_0
+    image: ivoanjo/docker-library:ddtrace_rb_jruby_9_2_0_0
     command: /bin/bash
     depends_on:
       - ddagent
@@ -270,7 +270,7 @@ services:
       - .:/app
       - bundle-jruby-9.2.0.0:/usr/local/bundle
   tracer-jruby-9.2-latest:
-    image: marcotc/docker-library:ddtrace_rb_jruby_9_2_11_1
+    image: ivoanjo/docker-library:ddtrace_rb_jruby_9_2_18_0
     command: /bin/bash
     depends_on:
       - ddagent

data/docs/GettingStarted.md

@@ -86,6 +86,9 @@ To contribute, check out the [contribution guidelines][contribution docs] and [d
          - [For application runtime](#for-application-runtime)
      - [OpenTracing](#opentracing)
      - [Profiling](#profiling)
+ - [Known issues and suggested configurations](#known-issues-and-suggested-configurations)
+    - [Payload too large](#payload-too-large)
+    - [Stack level too deep](#stack-level-too-deep)
 
 ## Compatibility
 
@@ -2237,7 +2240,7 @@ In many cases, such as logging, it may be useful to correlate trace IDs to other
 
 ##### Automatic
 
-For Rails applications using the default logger (`ActiveSupport::TaggedLogging`) or `lograge`, you can automatically enable trace correlation injection by setting the `rails` instrumentation configuration option `log_injection` to `true` or by setting environment variable `DD_LOGS_INJECTION=true`:
+For Rails applications using the default logger (`ActiveSupport::TaggedLogging`), `semantic_logger`, or `lograge`, you can automatically enable trace correlation injection by setting the `rails` instrumentation configuration option `log_injection` to `true` or by setting environment variable `DD_LOGS_INJECTION=true`:
 
 ```ruby
 # config/initializers/datadog.rb
@@ -2248,8 +2251,6 @@ Datadog.configure do |c|
 end
 ```
 
-_Note:_ For `lograge` users who have also defined `lograge.custom_options` in an `initializers/lograge.rb` configuration file, due to the order that Rails loads initializers (alphabetical), automatic trace correlation may not take effect, since `initializers/datadog.rb` would be overwritten by the `initializers/lograge.rb` initializer. To support automatic trace correlation with _existing_ `lograge.custom_options`, use the [Manual (Lograge)](#manual-lograge) configuration below.
-
 ##### Manual (Lograge)
 
 After [setting up Lograge in a Rails application](https://docs.datadoghq.com/logs/log_collection/ruby/), manually modify the `custom_options` block in your environment configuration file (e.g. `config/environments/production.rb`) to add the trace IDs.
@@ -2409,7 +2410,7 @@ The tracer and its integrations can produce some additional metrics that can pro
 To configure your application for metrics collection:
 
 1. [Configure your Datadog agent for StatsD](https://docs.datadoghq.com/developers/dogstatsd/#setup)
-2. Add `gem 'dogstatsd-ruby', '~> 4.0'` to your Gemfile (note that it is advised to pin v4.x [until this issue is solved](https://github.com/DataDog/dogstatsd-ruby/issues/182))
+2. Add `gem 'dogstatsd-ruby', '~> 5.2'` to your Gemfile
 
 #### For application runtime
 
@@ -2495,3 +2496,33 @@ To get started with profiling, follow the [Profiler Getting Started Guide](https
 When profiling [Resque](https://github.com/resque/resque) jobs, you should set the `RUN_AT_EXIT_HOOKS=1` option described in the [Resque](https://github.com/resque/resque/blob/v2.0.0/docs/HOOKS.md#worker-hooks) documentation.
 
 Without this flag, profiles for short-lived Resque jobs will not be available as Resque kills worker processes before they have a chance to submit this information.
+
+## Known issues and suggested configurations
+
+### Payload too large
+
+By default, Datadog limits the size of trace payloads to prevent memory overhead within instrumented applications. As a result, traces containing thousands of operations may not be sent to Datadog.
+
+If traces are missing, enable [debug mode](#tracer-settings) to check if messages containing `"Dropping trace. Payload too large"` are logged.
+
+Since debug mode is verbose, Datadog does not recommend leaving this enabled or enabling this in production. Disable it after confirming. You can inspect the [Datadog Agent logs](https://docs.datadoghq.com/agent/guide/agent-log-files/) for similar messages.
+
+If you have confirmed that traces are dropped due to large payloads, then enable the [partial_flush](#tracer-settings) setting to break down large traces into smaller chunks.
+
+### Stack level too deep
+
+Datadog tracing collects trace data by adding instrumentation into other common libraries (e.g. Rails, Rack, etc.) Some libraries provide APIs to add this instrumentation, but some do not. In order to add instrumentation into libraries lacking an instrumentation API, Datadog uses a technique called "monkey-patching" to modify the code of that library.
+
+In Ruby version 1.9.3 and earlier, "monkey-patching" often involved the use of [`alias_method`](https://ruby-doc.org/core-3.0.0/Module.html#method-i-alias_method), also known as *method rewriting*, to destructively replace existing Ruby methods. However, this practice would often create conflicts & errors if two libraries attempted to "rewrite" the same method. (e.g. two different APM packages trying to instrument the same method.)
+
+In Ruby 2.0, the [`Module#prepend`](https://ruby-doc.org/core-3.0.0/Module.html#method-i-prepend) feature was introduced. This feature avoids destructive method rewriting and allows multiple "monkey patches" on the same method. Consequently, it has become the safest, preferred means to "monkey patch" code.
+
+Datadog instrumentation almost exclusively uses the `Module#prepend` feature to add instrumentation non-destructively. However, some libraries (typically those supporting Ruby < 2.0) still use `alias_method` which can create conflicts with Datadog instrumentation, often resulting in `SystemStackError` or `stack level too deep` errors.
+
+As the implementation of `alias_method` exists within those libraries, Datadog generally cannot fix them. However, some libraries have known workarounds:
+
+* `rack-mini-profiler`: [Net::HTTP stack level too deep errors](https://github.com/MiniProfiler/rack-mini-profiler#nethttp-stack-level-too-deep-errors).
+
+For libraries without a known workaround, consider removing the library using `alias` or `Module#alias_method` or separating libraries into different environments for testing.
+
+For any further questions or to report an occurence of this issue, please [reach out to Datadog support](https://docs.datadoghq.com/help)