Ktor: support setting custom spanNameExtractor (#12842)
#12850
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
The committers listed above are authorized under a signed CLA. |
trask
approved these changes
Dec 9, 2024
laurit
reviewed
Dec 10, 2024
| @@ -86,6 +87,10 @@ abstract class AbstractKtorServerTracingBuilder(private val instrumentationName: | |||
| } | |||
| } | |||
|
|
|||
| fun spanNameExtractor(spanNameExtractorTransformer: Function<SpanNameExtractor<in ApplicationRequest>, out SpanNameExtractor<in ApplicationRequest>>) { | |||
There was a problem hiding this comment.
@trask just a note: setEmitExperimentalHttpServerMetrics is also missing
laurit
approved these changes
Dec 10, 2024
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 support for custom
SpanNameExtractors in the Ktor instrumentation modules. It should support both Ktor 2 and 3.See #12842 for more context.