chore: Add ddog documentation for OpenTelemetry #16114
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 improves our OpenTelemetry documentation and adds DataDog example. In general open-telemetry and tracing are advanced topics and it is mostly a developer topic and not really a user topic as the action items are usually for developers to improve scheduling or do code changes. for user we need to provide different information like time for each table as the only thing a user can do is add/remove tables and split the workload better (splitting the workload ideally shouldn't be a thing user is doing as well but we are not there yet with distributed scheduling).