Continuous Profiler for AWS Lambda

Docs > サーバーレス > AWS Lambda のためのサーバーレスモニタリング > Continuous Profiler for AWS Lambda

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Datadog’s Continuous Profiler for AWS Lambda functions gives you visibility into the exact method name, class name, and line number in your Lambda code that is causing CPU or I/O bottlenecks.

Continuous Profiler for AWS Lambda is in public beta. During the beta period, profiling for Node and Python is available at no additional cost.

Usage

To enable profiling:

Ensure you have installed the associated tracing library in your Lambda function.
Set the DD_PROFILING_ENABLED environment variable to true.

Data is available after a minimum of 60 execution seconds of the Lambda function.

The profiler works by spawning a thread that periodically wakes up and takes a snapshot of the CPU and heap of running code. This includes the profiler itself. If you want the profiler to ignore itself, set DD_PROFILING_IGNORE_PROFILER to true.