- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
A flare allows you to send necessary troubleshooting information to the Datadog support team, including tracer logs, with sensitive data removed. Flares are useful for troubleshooting issues like high CPU usage, high memory usage, and missing spans.
1.26.0
or greater2.11.0
or greater5.15.0
or greater, or 4.39.0
or greater2.46.0
or greaterTo send a flare from the Datadog site, make sure you’ve enabled Fleet Automation and Remote Configuration on the Agent. To send a remote flare:
For example:
Use Datadog debug settings to diagnose issues or audit trace data. Datadog does not recommend that you enable debug mode in production systems because it increases the number of events that are sent to your loggers. Use debug mode for debugging purposes only.
Debug mode is disabled by default. To enable it, follow the corresponding language tracer instructions:
To enable debug mode for the Datadog Node.js Tracer, use the environment variable DD_TRACE_DEBUG=true
.
Note: For versions below 2.X, debug mode could be enabled programmatically inside the tracer initialization but this is no longer supported.
Application Logs
In debug mode the tracer will log debug information to console.log()
and errors to console.error()
. You can change this behavior by passing a custom logger to the tracer. The logger should contain debug()
and error()
methods that can handle messages and errors, respectively.
For example:
const bunyan = require('bunyan')
const logger = bunyan.createLogger({
name: 'dd-trace',
level: 'trace'
})
const tracer = require('dd-trace').init({
logger: {
debug: message => logger.trace(message),
error: err => logger.error(err)
}
})
Then check the Agent logs to see if there is more info about your issue:
If the trace was sent to the Agent properly, you should see Response from the Agent: OK
log entries. This indicates that the tracer is working properly, so the problem may be with the Agent itself. Refer to the Agent troubleshooting guide for more information.
If an error was reported by the Agent (or the Agent could not be reached), you will see Error from the Agent
log entries. In this case, validate your network configuration to ensure the Agent can be reached. If you are confident the network is functional and that the error is coming from the Agent, refer to the Agent troubleshooting guide.
If neither of these log entries is present, then no request was sent to the Agent, which means that the tracer is not instrumenting your application. In this case, contact Datadog support and provide the relevant log entries with a flare.
For more tracer settings, check out the API documentation.
When debug mode for your tracer is enabled, tracer-specific log messages report how the tracer was initialized and whether traces were sent to the Agent. Debug logs are stored in a separate path depending on your logging configuration. If you enable application-level tracer information, debug logs are also sent in the flare for supported languages. The following log examples show what might appear in your log file.
If there are errors that you don’t understand, or if traces are reported as flushed to Datadog but you cannot see them in the Datadog UI, contact Datadog support and provide the relevant log entries with a flare.
Issue sending trace to the Agent:
{
"name": "dd-trace",
"hostname": "<hostname>",
"pid": 28817,
"level": 50,
"err": {
"message": "Network error trying to reach the agent: connect ECONNREFUSED 127.0.0.1:8126",
"name": "Error",
"stack": "Error: Network error trying to reach the agent: connect ECONNREFUSED 127.0.0.1:8126\n at ClientRequest.req.on.e (/path/to/dd-trace/src/platform/node/request.js:44:33)\n at scope.activate (/path/to/dd-trace/packages/dd-trace/src/scope/base.js:68:19)\n at Scope._activate (/path/to/dd-trace/packages/dd-trace/src/scope/base.js:44:14)\n at Scope.activate (/path/to/dd-trace/packages/dd-trace/src/scope/base.js:13:17)\n at ClientRequest.<anonymous> (/path/to/dd-trace/packages/dd-trace/src/scope/base.js:67:20)\n at ClientRequest.emit (events.js:193:13)\n at ClientRequest.req.emit (/path/to/dd-trace/packages/datadog-plugin-http/src/client.js:93:21)\n at Socket.socketErrorListener (_http_client.js:397:9)\n at Socket.emit (events.js:198:15)\n at emitErrorNT (internal/streams/destroy.js:91:8)"
},
"msg": "Network error trying to reach the agent: connect ECONNREFUSED 127.0.0.1:8126",
"time": "2019-08-06T20:48:27.769Z",
"v": 0
}
추가 유용한 문서, 링크 및 기사: