Add telemetry to api server #28
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
GregMefford
reviewed
Jan 15, 2021
Merged
GregMefford
reviewed
Jan 18, 2021
It's not used anywhere AFAICT and it makes testing much more difficult.
GregMefford
reviewed
Jan 18, 2021
|
Hm, working on getting it to reliably crash and fire the |
zachdaniel
approved these changes
Jan 18, 2021
GregMefford
force-pushed
the
add-telemetry
branch
from
70353b7
to
4f85b56
Compare
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 adds telemetry spans to the api server. My hypothesis is that the API Server is a bottleneck on the system and adding substantial overhead under high load scenarios. This telemetry should help to prove or disprove my hypothesis.