fix(traces): Drop aggregated trace data on API key failure to reduce memory usage #787
Conversation
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
…sary memory usage.
…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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.