- 重要な情報
- はじめに
- 用語集
- エージェント
- インテグレーション
- OpenTelemetry
- 開発者
- API
- CoScreen
- アプリ内
- インフラストラクチャー
- アプリケーションパフォーマンス
- 継続的インテグレーション
- ログ管理
- セキュリティ
- UX モニタリング
- 管理
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.
The Datadog Profiler requires at least Node.js 14, but Node.js 16 or higher is recommended. If you use a version of Node.js earlier than 16, some applications see tail latency spikes every minute when starting the next profile.
Continuous Profiler is not supported on serverless platforms, such as AWS Lambda.
To begin profiling applications:
If you are already using Datadog, upgrade your Agent to version 7.20.2+ or 6.20.2+.
Run npm install --save dd-trace@latest
to add a dependency on the dd-trace
module which includes the profiler.
Enable the profiler:
export DD_PROFILING_ENABLED=true
export DD_ENV=prod
export DD_SERVICE=my-web-app
export DD_VERSION=1.0.3
Note: If you’re already using Datadog APM, you are already calling init
and don’t need to do so again. If you are not, ensure the tracer and the profiler are loaded together:
node -r dd-trace/init app.js
const tracer = require('dd-trace').init({
profiling: true,
env: 'prod',
service: 'my-web-app',
version: '1.0.3'
})
Note: If you’re already using Datadog APM, you are already calling init
and don’t need to do so again. If you are not, ensure the tracer and the profiler are loaded together:
const tracer = require('dd-trace/init')
A minute or two after starting your Node.js application, your profiles will show up on the APM > Profiler page.
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.
Node.js 16 or higher is recommended. On earlier versions, some applications see tail latency spikes every minute while starting the next profile.