Document Tracing without Limits #1455
Merged
Conversation
This file contains 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
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.
This PR documents the transition from the deprecated App Analytics to Tracing without Limits™.
New users are encouraged to enable Tracing without Limits™ in new deployments, as this provides much better control over trace retention and ingestion.
App Analytics users are still supported and encouraged to migrate, but migration might require decisions in the Datadog app around trace retention that can affect billing. Given this, we do not want to emit a deprecation warning to all clients without a concrete actionable, which we don't have at this moment.
Changing the default to enable Tracing without Limits™ would be ideal, but it's a breaking change that affects billing, so this change is not being done here.