Bump ddtrace from 1.18.0 to 1.19.0

[dependabot]

Bumps ddtrace from 1.18.0 to 1.19.0.

Release notes

Sourced from ddtrace's releases.

1.19.0

Highlights

Alpha support for Memory Profiling (Allocations and Heap)

As of ddtrace 1.19.0, the Profiler supports three new profile types:

• Allocations
• Heap Live Objects
• Heap Live Size

You can use these to optimize your application to allocate and use less memory, as well as to track down memory leaks.

We're still working on tuning the overhead impact and sampling frequency for these new profile types, and that's why this feature is marked as experimental.

You can enable these features:

• Using the environment variables DD_PROFILING_EXPERIMENTAL_ALLOCATION_ENABLED=true, DD_PROFILING_EXPERIMENTAL_HEAP_ENABLED=true and DD_PROFILING_EXPERIMENTAL_HEAP_SIZE_ENABLED=true
• Or via code by adding to your Datadog.configure block:

Datadog.configure do |c|
  # ... existing configuration ...
  c.profiling.advanced.experimental_allocation_enabled = true
  c.profiling.advanced.experimental_heap_enabled = true
  c.profiling.advanced.experimental_heap_size_enabled = true
end

Known issues and limitations:

• This feature only works on Ruby 2.7 and above.
• Ruby versions 3.2.0, 3.2.1 and 3.2.2 are not supported due to a Ruby VM bug. The bug has been fixed upstream and the upcoming Ruby 3.2.3 will be supported.
• This feature is currently incompatible with applications using Ractors due to a Ruby VM bug.
• The three options above are not fully independent; experimental_heap_size_enabled requires experimental_heap_enabled, and in turn experimental_heap_enabled requires experimental_allocation_enabled.
• We have added experimental tunables for lowering the overhead of these features. For more details, check the documentation for the experimental_allocation_sample_rate and experimental_heap_sample_rate settings.
• The experimental_allocation_enabled feature replaces the allocation_counting_enabled setting, which is now deprecated.

We're very interested in feedback on how this feature works for you. Give it a try, let us know how it's working!

Performance improvements to Garbage Collection Profiling + Timeline view support

The off-by-default Garbage Collection profiling feature has been redesigned to lower its overhead, and to support showing time spent doing Garbage Collection in the Profiler Timeline view.

See DataDog/dd-trace-rb#3313 for some nice screenshots of how it looks!

You can enable this feature using the DD_PROFILING_FORCE_ENABLE_GC=true environment variable, or using the

... (truncated)

Changelog

Sourced from ddtrace's changelog.

[1.19.0] - 2024-01-10

Highlights

Alpha support for memory profiling has been added. For more details, check the release notes

Added

• Tracing: Add on_error settings for mysql2 (#3316[])
• Core: Add install_signature to app-started telemetry event (#3349[])
• Profiling: Heap Profiling (#3281[]) (#3287[]) (#3328[]) (#3329[]) (#3333[]) (#3360[])
• Profiling: Redesign GC profiling to add timeline support and reduce overhead (#3313[])
• Core: Use Ruby 3.3 stable for CI testing (#3354[])

Changed

• Core: Bump datadog-ci dependency to 0.6.0 (#3361[])
• Core: Bump debase-ruby_core_source dependency to 3.3.1 (#3373[])
• Docs: Backport "List Ruby 3.3 as supported in the docs" to master branch (#3374[])
• Profiling: Import upstream rb_profile_frames fix (#3352[])
• Profiling: Allow the dynamic sampling rate overhead target to be set (#3310[])
• Profiling: Split profiling tests into ractor and non-ractor suites. (#3320[])

Fixed

• Docs: Fix pg doc markdown format (#3317[])
• Tracing: Fix recursive require in Railtie (#3365[])
• Profiling: Fix issues stemming from rb_gc_force_recycle (#3366[])
• Profiling: Fix Ruby 3.3 CI being broken in master due to profiler (#3356[])
• Profiling: Fix "no signals" workaround detection when mariadb is in use (#3362[])

Commits

• ef61baf Merge pull request #3378 from DataDog/bump_to_version_1.19.0
• f3c3408 Update lockfiles for ddtrace 1.19.0
• 2b57bc4 Bump version 1.18.0 to 1.19.0
• d1869f4 Add 1.19.0 to CHANGELOG.md
• d4ed0ec Merge pull request #3377 from DataDog/ivoanjo/skip-ractor-tests
• cdaf44d [NO-TICKET] Minor: Skip testcases using ractors when calling RSpec directly
• fd56a11 Merge pull request #3374 from DataDog/ivoanjo/backport-ruby3-docs
• fedfe82 Add Ruby 3.3 as supported
• 8d88686 Merge pull request #3373 from DataDog/ivoanjo/bump-debase-ruby-core-source-3_3_1
• b0f9de9 Bump debase-ruby_core_source dependency to 3.3.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions