fix(traces): Drop aggregated trace data on API key failure to reduce memory usage by litianningdatadog · Pull Request #787 · DataDog/datadog-lambda-extension
Navigation Menu
{{ message }}
DataDog / datadog-lambda-extension Public
- Notifications You must be signed in to change notification settings
- Fork 17
Merged
Conversation
Copy link
Contributor
In case of API key failure, we should drop the aggregated tracing data as there is no way to send them back. By doing so we expect to reduce the memory wasted on the unsent data.
Tested with fullinstrument stack in self-monitor repo. Manifest. Below chart shows the memory usage reduced with the proposed change.
…sary memory usage.
litianningdatadog
requested a review
from a team
as a code owner
litianningdatadog added 4 commits
August 15, 2025 14:35…sary memory usage.
…datadog-lambda-extension into tianning.li/purge-trace-flusher
…datadog-lambda-extension into tianning.li/purge-trace-flusher
…datadog-lambda-extension into tianning.li/purge-trace-flusher
duncanista approved these changes Aug 15, 2025
duncanista
changed the title
fix: Drop aggregated trace data on API key failure to reduce memory usage
fix(traces): Drop aggregated trace data on API key failure to reduce memory usage
litianningdatadog
deleted the
tianning.li/purge-trace-flusher
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants