feat: Add utilities to query transaction data from Sentry - #39
Merged
Conversation
tustanivsky
marked this pull request as ready for review
February 17, 2026 12:57
limbonaut
approved these changes
Feb 17, 2026
limbonaut
left a comment
Collaborator
There was a problem hiding this comment.
README could use an update. Aside from that, LGTM.
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
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 new utility functions to the
sentry-api-clientmodule that allow querying tracing data (transactions/spans) from Sentry for use in integration tests.Key changes:
Get-SentrySpanstosentry-api-clientfor querying spans (including transactions) via the Sentry Discover API (dataset=spans), supporting filtering by trace ID, query string, time range, and custom fieldsGet-SentryTestTransactionpolling helper toIntegration.TestUtilsthat retrieves a full transaction event by trace ID (with tags, child spans, and contexts) using a two-step flow: find the transaction span, then fetch the complete event detailGet-SentrySpansfunctionRelated items:
#skip-changelog