- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
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.
To enable profiling:
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
.
Depending on your runtime, this feature requires the following tracer and layer versions:
Runtime | Minimum tracer version | Minimum layer version |
---|---|---|
Python | 1.4.0 | 62 |
Node.js | 2.22.1, 3.9.0 | 87 |
Additional helpful documentation, links, and articles: