feat(nestjs): Use more specific span origins for NestJS guards, pipes, interceptors, and exception filters#19751
Merged
nicohrubec merged 1 commit intodevelopfrom Mar 11, 2026
Conversation
…, interceptors, and exception filters
Contributor
size-limit report 📦
|
Lms24
approved these changes
Mar 11, 2026
andreiborza
pushed a commit
that referenced
this pull request
Mar 11, 2026
…, interceptors, and exception filters (#19751) This should allow for more specific querying for users and also potentially interesting data to look at for us in the future. Spans emitted from actual middlewares keep the same origin as before, for the rest I added the integration-part so we know where the span is coming from. Closes #19750
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
3 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.
This should allow for more specific querying for users and also potentially interesting data to look at for us in the future. Spans emitted from actual middlewares keep the same origin as before, for the rest I added the integration-part so we know where the span is coming from.
Closes #19750