Add support for Apollo server tracing in GraphQL #2485
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
derrickmehaffy
changed the title
|
@lauriejim This PR is a simple one just add another config option to GraphQL to support time traces on specific queries. It can dramatically increase the size of the response but is disabled by default so there should be no breaking issues if you wanted to include this in the next release. |
lauriejim
added
pr: 🚀 New feature
source: core:content-manager
|
I will let @Aurelsicoko take the decision about that. |
Aurelsicoko
approved these changes
Dec 20, 2018
|
LGTM 👍 |
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.
My PR is a:
Main update on the:
This adds support for the Apollo server tracing feature to assist users and developers track parts of a graphQL query to see where any latency is happening.
By default it is off, but can be enabled if needed.