The profiler is shipped within Datadog tracing libraries. If you are already using APM to collect traces for your application, you can skip installing the library and go directly to enabling the profiler.

Requirements

For a summary of the minimum and recommended runtime and tracer versions across all languages, read Supported Language and Tracer Versions.

The Datadog Profiler requires Ruby 2.5+ (Ruby 3.1+ or later is recommended). JRuby and TruffleRuby are not supported.

The following operating systems and architectures are supported:

• Linux (GNU libc) x86-64, aarch64
• Alpine Linux (musl libc) x86-64, aarch64

You also need either the pkg-config or the pkgconf system utility installed. This utility is available on the software repositories of most Linux distributions. For example:

• The pkg-config package is available for Homebrew, and Debian- and Ubuntu-based Linux
• The pkgconf package is available for Arch- and Alpine-based Linux
• The pkgconf-pkg-config package is available for Fedora- and Red-Hat-based Linux

Continuous Profiler is not supported on serverless platforms, such as AWS Lambda.

Installation

To begin profiling applications:

1. Ensure Datadog Agent v6+ is installed and running. Datadog recommends using Datadog Agent v7+.

2. Add the datadog gem to your Gemfile or gems.rb file:

   gem 'datadog', '~> 2.7'
   

3. Install the gems with bundle install.

4. Enable the profiler:

   • Environment variables
   • In code

   export DD_PROFILING_ENABLED=true
   export DD_ENV=prod
   export DD_SERVICE=my-web-app
   export DD_VERSION=1.0.3
   

   Copy

   Datadog.configure do |c|
     c.profiling.enabled = true
     c.env = 'prod'
     c.service = 'my-web-app'
     c.version = '1.0.3'
   end
   

   Note: For Rails applications, create a config/initializers/datadog.rb file with the code configuration above.

5. Add the ddprofrb exec command to your Ruby application start command:

   bundle exec ddprofrb exec ruby myapp.rb
   

   Copy

   Rails example:

   bundle exec ddprofrb exec bin/rails s
   

   Copy

   If you’re running a version of the gem older than 1.21.0, replace ddprofrb exec with ddtracerb exec.

   Note

   If starting the application with ddprofrb exec is not an option (for example, when using the Phusion Passenger web server), you can alternatively start the profiler by adding the following to your application entry point (such as config.ru, for a web application):

   require 'datadog/profiling/preload'
   

6. Optional: Set up Source Code Integration to connect your profiling data with your Git repositories.

7. A minute or two after starting your Ruby application, your profiles will show up on the Datadog APM > Profiler page.

Configuration

These settings apply to the latest profiler release.

You can configure the profiler using the following environment variables:

Alternatively, you can set profiler parameters in code with these functions, inside a Datadog.configure block:

Not sure what to do next?

The Getting Started with Profiler guide takes a sample service with a performance problem and shows you how to use Continuous Profiler to understand and fix the problem.

Further Reading

Additional helpful documentation, links, and articles:

Getting Started with ProfilerDOCUMENTATION Learn more about available profile visualizationsDOCUMENTATION Fix problems you encounter while using the profilerDOCUMENTATION Analyze Ruby code performance with Datadog Continuous ProfilerBLOG