Update viewed traces retention policy #32614
Conversation
Preview links (active after the
|
| - **Indexed spans**: 15 or 30 days, determined by customer plan | ||
| - **Services/resources statistics**: 30 days | ||
| - **Viewed traces**: 15 months | ||
| - **Viewed traces**: Retained for the duration of the account |
There was a problem hiding this comment.
Which account is this referencing?
There was a problem hiding this comment.
We retain viewed trace information as long as the customer’s Datadog account remains active. (in other words, forever, unless they demand to delete their account)
I see that other products used "Retained for the duration of the account" wording so I put the same for the sake of consistency. Feel free to change it to something else, I don't have a strong opinion to keeo this version.
There was a problem hiding this comment.
Ah okay, thanks for explaining. It'd probably be better to be more specific like what you said, "Retained as long as the Datadog account remains active", but for consistency, I'm fine with it.
| - **Indexed spans**: 15 or 30 days, determined by customer plan | ||
| - **Services/resources statistics**: 30 days | ||
| - **Viewed traces**: 15 months | ||
| - **Viewed traces**: Retained for the duration of the account |
There was a problem hiding this comment.
Ah okay, thanks for explaining. It'd probably be better to be more specific like what you said, "Retained as long as the Datadog account remains active", but for consistency, I'm fine with it.
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes