Add spans for ResolveHost and ProfileExists#233
Open
carole-lavillonniere wants to merge 1 commit intofix-telemetryfrom
Open
Add spans for ResolveHost and ProfileExists#233carole-lavillonniere wants to merge 1 commit intofix-telemetryfrom
carole-lavillonniere wants to merge 1 commit intofix-telemetryfrom
Conversation
anisaoshafi
approved these changes
May 7, 2026
Contributor
anisaoshafi
left a comment
anisaoshafi
left a comment
There was a problem hiding this comment.
Good job! already using otel to investigate performance issues🏅
This file contains hidden or 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
2 participants
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.
Motivation
Trace of
lstk awsshows ~100ms gap between Docker container check andaws clispan start. See #231Untraced work in that window: DNS lookup in
endpoint.ResolveHostplus~/.aws/configreads inawsconfig.ProfileExists. Adding spans makes the gap visible.Towards DRG-809