Continuous Profiler
Incident Management is now generally available! Incident Management is now generally available!

Continuous Profiler

Exploring profiling flame graph

Find CPU, memory, and IO bottlenecks, broken down by method name, class name, and line number, to significantly reduce end-user latency and infrastructure costs.

Low impact in production

Continuous profiler is designed to run in production across all services by leveraging technologies such as JDK Flight Recorder to have minimal impact on your host’s CPU and memory usage.

Getting Started

Profiling your service to visualize all your stack traces in one place takes just minutes.

1. Instrument Your Application

Add a profiler library to your application to start sending profiles to the Datadog Agent.

To get notified when a private beta is available for the Node, Ruby, PHP, or .NET Profiler, sign up here.

Explore Datadog Profiler

Now that you’ve configured your application to send profiles to Datadog, start getting insights into your code performance:

Search profiles by tags

Use tags to search profiles across any dimension—whether it’s a specific host, service, version, or any combination.

Search profiles by tags

Track function performance over deployments

Obtain key profiling metrics from services such as top CPU usage by method, top memory allocations by thread, and CPU usage by version to visualize in your dashboards.

Add profiling metrics to your dashboards.

Connect traces to profiling data

Application processes that have both APM distributed tracing and continuous profiler enabled are automatically linked, so you can move directly from span information to profiling data on the Code Hotspots tab to find specific lines of code related to performance issues.

Code Hotspots tab shows profiling information for a APM trace span

Further Reading