chore(preprod): Set default data EAP retention to 13 months #105646
+7
−4
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
github-actions
bot
added
the
Scope: Backend
NicoHinderling
commented
Jan 5, 2026
| from sentry.utils.arroyo_producer import SingletonProducer, get_arroyo_producer | ||
| from sentry.utils.kafka_config import get_topic_definition | ||
|
|
||
| THIRTEEN_MONTHS = 396 # 13 months in days |
Contributor
Author
There was a problem hiding this comment.
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
| trace_id=trace_id, | ||
| received=received, | ||
| retention_days=90, # Default retention for preprod data | ||
| retention_days=THIRTEEN_MONTHS, # Default retention for preprod data |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
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.
While we wait for the billing code to be implemented so we can have proper retention values set based off the plan type, we should use the default max retention so that enterprise customers don't start losing size data when they shouldn't have
better to trim down retention later than the opposite