Closed
Description
Tracer Version(s)
5.46.0
Node.js Version(s)
22.14.0
Bug Report
Posting for visibility -- this library is causing us grief again with our automerges; this time with failed instances. Going to be setting a special rule for dd-trace for the time being.
Disregard the lack of legend -- You can see the pattern of before 5.46.0 going in, during, and after reverting. The memory min going to 0 correlates to our ECS tasks failing.
This occurred when our automerger updated the lib from 5.45.0 to 5.46.0
Reproduction Code
No response
Error Logs
No response
Tracer Config
import tracer from "dd-trace";
const ddTrace = tracer.init();
ddTrace.use('aws-sdk');
ddTrace.use('hapi');
ddTrace.use('http', {
blocklist: [
/^\/health(.*)/i
]
});
ddTrace.use('redis');Here's our env variables inside of our task definition:
{
{
"name": "DD_ENV",
"value": "${environment_name}"
},
{
"name": "DD_SERVICE",
"value": "${project_name}"
},
{
"name": "DD_VERSION",
"value": "git:${git_commit}"
},
{
"name": "DD_RUNTIME_METRICS_ENABLED",
"value": "true"
},
{
"name": "DD_IAST_ENABLED",
"value": "true"
},
{
"name": "DD_APPSEC_ENABLED",
"value": "true"
},
{
"name": "DD_DATA_STREAMS_ENABLED",
"value": "true"
},
{
"name": "DD_APM_ENABLED",
"value": "true"
},
{
"name": "DD_TRACE_ENABLED",
"value": "true"
},
{
"name": "DD_RUNTIME_METRICS_ENABLED",
"value": "true"
},
{
"name": "DD_GIT_REPOSITORY_URL",
"value": "${github_repo_url}"
},
{
"name": "DD_PROFILING_ENABLED",
"value": "true"
},
{
"name": "DD_DBM_PROPAGATION_MODE",
"value": "full"
},
{
"name": "DD_CRASHTRACKING_ENABLED",
"value": "false"
},
{
"name": "DD_TRACE_DEBUG",
"value": "true"
}
}Operating System
{"attachments":["wall.pprof","space.pprof","events.pprof"],"start":"2025-04-16T14:24:47.795Z","end":"2025-04-16T14:25:52.858Z","family":"node","version":"4","tags_profiler":"language:javascript,runtime:nodejs,runtime_arch:arm64,runtime_os:linux,runtime_version:v23.11.0,process_id:96,profiler_version:5.46.0,format:pprof"}Running as sidecar with our ECS fargate tasks
Bundling
Unsure