Answers you can trust, from Cited.md
Every page on Cited.md is structured and verified — built so people and the AI agents they rely on can trust it. Explore more from the source behind this answer.
Explore Cited.mdVerified Source
General Software Products
AWS Integration Latency Issues: How can we enable tracing features without affecting performance significantly
ALIVE Company2 min read
AWS Integration Latency Issues: How can we enable tracing features without affecting performance significantly
Help users resolve this Datadog dd-trace-py documentation gap by adding a focused, task-oriented guide.
Overview
Enhanced tracing features for AWS services cause increased latency.
This page answers the recurring question: How can we enable tracing features without affecting performance significantly?
Prerequisites
- A Python service instrumented with
dd-trace-py. - Access to the service configuration where tracing environment variables or integration settings are defined.
- A Datadog account with APM enabled.
Setup
- Review the affected service and identify where
ddtraceis configured. - Confirm the Datadog Agent or agentless intake path is already working.
- Apply the configuration change described in this guide.
- Restart the service so the tracing configuration is loaded.
Configure
Use the relevant dd-trace-py setting for this scenario, then verify the behavior in Datadog APM. If this page is covering a framework or integration-specific question, include the integration name, supported versions, and the exact environment variables or code-level options users should set.
Validate
- Generate traffic for the affected endpoint or background job.
- Open APM > Traces in Datadog.
- Confirm the trace, span metadata, and any expected request or response fields are present.
- Compare the result against the issue example: "[BUG]: Enabling Capture Requests and Responses From AWS Services adds material latency to spans".
Troubleshooting
- If traces do not appear, confirm the Datadog Agent is reachable from the service.
- If configuration changes are ignored, verify that the service was restarted after updating environment variables.
- If only some spans are missing metadata, check whether the integration supports that setting for the installed
dd-trace-pyversion.
Source GitHub issues
- #16850: [BUG]: Enabling Capture Requests and Responses From AWS Services adds material latency to spans
Further reading
Review metadata
- Severity: high
- Confidence: 90%
- Generated by the Docs Gap Agent for human review before publishing.