Class: Datadog::Core::Configuration::Settings::DSL::Profiling::Advanced

Inherits:
Object
  • Object
show all
Defined in:
lib/datadog/core/configuration/settings.rb

Defined Under Namespace

Classes: Endpoint

Instance Attribute Summary collapse

Instance Method Summary collapse

Instance Attribute Details

#allocation_counting_enabledObject

Can be used to enable/disable the Datadog::Profiling.allocation_count feature.

Requires allocation profiling to be enabled.

Defaults to:

  • false



310
311
312
# File 'lib/datadog/core/configuration/settings.rb', line 310

def allocation_counting_enabled
  @allocation_counting_enabled
end

#code_provenance_enabledObject

Can be used to disable the gathering of names and versions of gems in use by the service, used to power grouping and categorization of stack traces.



284
285
286
# File 'lib/datadog/core/configuration/settings.rb', line 284

def code_provenance_enabled
  @code_provenance_enabled
end

#dir_interruption_workaround_enabledObject

The profiler gathers data by sending SIGPROF unix signals to Ruby application threads.

We've discovered that this can trigger a bug in a number of Ruby APIs in the Dir class, as described in https://bugs.ruby-lang.org/issues/20586 . This was fixed for Ruby 3.4+, and this setting is a no-op for those versions.

otherwise true

Defaults to:

  • DD_PROFILING_DIR_INTERRUPTION_WORKAROUND_ENABLED environment variable as a boolean,



421
422
423
# File 'lib/datadog/core/configuration/settings.rb', line 421

def dir_interruption_workaround_enabled
  @dir_interruption_workaround_enabled
end

#experimental_crash_tracking_enabledObject

DEV-3.0: Remove experimental_crash_tracking_enabled option



456
457
458
# File 'lib/datadog/core/configuration/settings.rb', line 456

def experimental_crash_tracking_enabled
  @experimental_crash_tracking_enabled
end

#experimental_heap_enabledObject

Can be used to enable/disable the collection of heap profiles.

This feature is in preview and disabled by default. Requires Ruby 3.1+.

Defaults to:

  • DD_PROFILING_EXPERIMENTAL_HEAP_ENABLED environment variable as a boolean, otherwise false



322
323
324
# File 'lib/datadog/core/configuration/settings.rb', line 322

def experimental_heap_enabled
  @experimental_heap_enabled
end

#experimental_heap_sample_rateObject

Can be used to configure the heap sampling rate: a heap sample will be collected for every x allocation samples.

The higher the value, the less accuracy in heap tracking but the smaller the overhead.

If you needed to tweak this, please tell us why on https://github.com/DataDog/dd-trace-rb/issues/new, so we can fix it!

The effective heap sampling rate in terms of allocations (not allocation samples) can be calculated via effective_heap_sample_rate = allocation_sample_rate * heap_sample_rate.

Defaults to:

  • DD_PROFILING_EXPERIMENTAL_HEAP_SAMPLE_RATE environment variable, otherwise 1.



354
355
356
# File 'lib/datadog/core/configuration/settings.rb', line 354

def experimental_heap_sample_rate
  @experimental_heap_sample_rate
end

#experimental_heap_size_enabledObject

Can be used to enable/disable the collection of heap size profiles.

This feature is in preview and by default is enabled whenever heap profiling is enabled.

follows the value of experimental_heap_enabled.

Defaults to:

  • DD_PROFILING_EXPERIMENTAL_HEAP_SIZE_ENABLED environment variable as a boolean, otherwise it



336
337
338
# File 'lib/datadog/core/configuration/settings.rb', line 336

def experimental_heap_size_enabled
  @experimental_heap_size_enabled
end

#gc_enabledObject

Can be used to enable/disable garbage collection profiling.

Defaults to:

  • DD_PROFILING_GC_ENABLED environment variable, otherwise true



299
300
301
# File 'lib/datadog/core/configuration/settings.rb', line 299

def gc_enabled
  @gc_enabled
end

#gvl_enabledObject

Controls GVL profiling. This will show when threads are waiting for GVL in the timeline view.

This feature requires Ruby 3.2+.

Defaults to:

  • DD_PROFILING_GVL_ENABLED environment variable as a boolean, otherwise true



487
488
489
# File 'lib/datadog/core/configuration/settings.rb', line 487

def gvl_enabled
  @gvl_enabled
end

#heap_clean_after_gc_enabledObject

Controls if the heap profiler should attempt to clean young objects after GC, rather than just at serialization time. This lowers memory usage and high percentile latency.

Only has effect when used together with gc_enabled: true and experimental_heap_enabled: true.

Defaults to:

  • true



543
544
545
# File 'lib/datadog/core/configuration/settings.rb', line 543

def heap_clean_after_gc_enabled
  @heap_clean_after_gc_enabled
end

#max_framesObject

Controls the maximum number of frames for each thread sampled. Can be tuned to avoid omitted frames in the produced profiles. Increasing this may increase the overhead of profiling.

Defaults to:

  • DD_PROFILING_MAX_FRAMES environment variable, otherwise 400



260
261
262
# File 'lib/datadog/core/configuration/settings.rb', line 260

def max_frames
  @max_frames
end

#native_filenames_enabledObject

Controls if the profiler should use native filenames for frames in stack traces for functions implemented using native code. Setting to false will make the profiler fall back to default Ruby stack trace behavior (only show .rb files).

Defaults to:

  • true



553
554
555
# File 'lib/datadog/core/configuration/settings.rb', line 553

def native_filenames_enabled
  @native_filenames_enabled
end

#no_signals_workaround_enabledObject

The profiler gathers data by sending SIGPROF unix signals to Ruby application threads.

Sending SIGPROF is a common profiling approach, and may cause system calls from native extensions/libraries to be interrupted with a system EINTR error code. Rarely, native extensions or libraries called by them may have missing or incorrect error handling for the EINTR error code.

The "no signals" workaround, when enabled, enables an alternative mode for the profiler where it does not send SIGPROF unix signals. The downside of this approach is that the profiler data will have lower quality.

This workaround is automatically enabled when gems that are known to have issues handling EINTR error codes are detected. If you suspect you may be seeing an issue due to the profiler's use of signals, you can try manually enabling this mode as a fallback. Please also report these issues to us on https://github.com/DataDog/dd-trace-rb/issues/new, so we can work with the gem authors to fix them!

Defaults to:

  • DD_PROFILING_NO_SIGNALS_WORKAROUND_ENABLED environment variable as a boolean, otherwise :auto



402
403
404
# File 'lib/datadog/core/configuration/settings.rb', line 402

def no_signals_workaround_enabled
  @no_signals_workaround_enabled
end

#overhead_target_percentageObject

Configures how much wall-time overhead the profiler targets. The profiler will dynamically adjust the interval between samples it takes so as to try and maintain the property that it spends no longer than this amount of wall-clock time profiling. For example, with the default value of 2%, the profiler will try and cause no more than 1.2 seconds per minute of overhead. Decreasing this value will reduce the accuracy of the data collected. Increasing will impact the application.

We do not recommend tweaking this value.

This value should be a percentage i.e. a number between 0 and 100, not 0 and 1.

Defaults to:

  • DD_PROFILING_OVERHEAD_TARGET_PERCENTAGE as a float, otherwise 2.0



438
439
440
# File 'lib/datadog/core/configuration/settings.rb', line 438

def overhead_target_percentage
  @overhead_target_percentage
end

#preview_gvl_enabledObject

Deprecated for removal.

Use :gvl_enabled instead.



468
469
470
# File 'lib/datadog/core/configuration/settings.rb', line 468

def preview_gvl_enabled
  @preview_gvl_enabled
end

#preview_otel_context_enabledObject

Controls if the profiler should attempt to read context from the otel library

Defaults to:

  • false



511
512
513
# File 'lib/datadog/core/configuration/settings.rb', line 511

def preview_otel_context_enabled
  @preview_otel_context_enabled
end

#sighandler_sampling_enabledObject

Controls if the profiler should sample directly from the signal handler. Sampling directly from the signal handler improves accuracy of the data collected.

We recommend using this setting with Ruby 3.2.5+ / Ruby 3.3.4+ and above as they include additional safety measures added in https://github.com/ruby/ruby/pull/11036. We have not validated it thoroughly with earlier versions, but in practice it should work on Ruby 3.0+ (the key change was https://github.com/ruby/ruby/pull/3296).

Enabling this on Ruby 2 is not recommended as it may cause VM crashes and/or incorrect data.

Defaults to:

  • true on Ruby 3.2.5+ / Ruby 3.3.4+, false on older Rubies



570
571
572
# File 'lib/datadog/core/configuration/settings.rb', line 570

def sighandler_sampling_enabled
  @sighandler_sampling_enabled
end

#skip_mysql2_checkObject

Can be used to disable checking which version of libmysqlclient is being used by the mysql2 gem.

This setting is only used when the mysql2 gem is installed.

Defaults to:

  • DD_PROFILING_SKIP_MYSQL2_CHECK environment variable, otherwise false



365
366
367
# File 'lib/datadog/core/configuration/settings.rb', line 365

def skip_mysql2_check
  @skip_mysql2_check
end

#timeline_enabledObject

Controls data collection for the timeline feature.

If you needed to disable this, please tell us why on https://github.com/DataDog/dd-trace-rb/issues/new, so we can fix it!

Defaults to:

  • DD_PROFILING_TIMELINE_ENABLED environment variable as a boolean, otherwise true



377
378
379
# File 'lib/datadog/core/configuration/settings.rb', line 377

def timeline_enabled
  @timeline_enabled
end

#upload_period_secondsObject

Controls how often the profiler reports data, in seconds. Cannot be lower than 60 seconds.

We do not recommend tweaking this value.

Defaults to:

  • DD_PROFILING_UPLOAD_PERIOD environment variable, otherwise 60



449
450
451
# File 'lib/datadog/core/configuration/settings.rb', line 449

def upload_period_seconds
  @upload_period_seconds
end

#waiting_for_gvl_threshold_nsObject

Controls the smallest time period the profiler will report a thread waiting for the GVL.

The default value was set to minimize overhead. Periods smaller than the set value will not be reported (e.g. the thread will be reported as whatever it was doing before it waited for the GVL).

We do not recommend setting this to less than 1ms. Tweaking this value can increase application latency and memory use.

Defaults to:

  • 10_000_000 (10ms)



503
504
505
# File 'lib/datadog/core/configuration/settings.rb', line 503

def waiting_for_gvl_threshold_ns
  @waiting_for_gvl_threshold_ns
end

Instance Method Details

#endpointDatadog::Core::Configuration::Settings::DSL::Profiling::Advanced::Endpoint

Returns a configuration object.



267
268
269
270
271
272
273
274
275
276
277
278
279
280
# File 'lib/datadog/core/configuration/settings.rb', line 267

settings :endpoint do
  settings :collection do
    # When using profiling together with tracing, this controls if endpoint names
    # are gathered and reported together with profiles.
    #
    # @default `DD_PROFILING_ENDPOINT_COLLECTION_ENABLED` environment variable, otherwise `true`
    # @return [Boolean]
    option :enabled do |o|
      o.env Profiling::Ext::ENV_ENDPOINT_COLLECTION_ENABLED
      o.default true
      o.type :bool
    end
  end
end