-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI Event Transactions - iOS and Android #4
Labels
Comments
5 tasks
bruno-garcia
changed the title
UI Event Transactions
UI Event Transactions - iOS and Android
May 9, 2022
5 tasks
This was referenced Jul 15, 2022
The only issue that stopped this from marking as closed is getsentry/sentry-cocoa#1977. We keep track of that issue in the Cocoa SDK and close this issue. |
github-project-automation
bot
moved this from Backlog
to Done
in Mobile & Cross Platform SDK
Mar 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The goal of UI transactions is to capture transactions based on user interactions. Currently, the offer of auto-generated transactions on mobile is limited, with only creating transactions when an app loads a screen. To provide more value, we want to extend the auto-generated transactions by generating transactions on UI events.
Internal Notion page. https://getsentry.atlassian.net/browse/MOBILE-239
UI Event Transaction
develop#647The default idle timeout is 3 seconds.
Scenarios
Scenarios are written in the Gherkin syntax.
Scenario: Discard UI event transactions without child spans
An empty transaction of a UI event doesn’t add any value.
Scenario: Set time to last finished child span
Scenario: Don't reset timeout when the second last span finishes
Scenario: Reset timeout when the last span finishes
Scenario: Cancel timeout when starting a span
Scenario: Ongoing screen load transaction
Scenario: Ongoing UI event transaction
Scenario: Manually created transaction on the scope
Scenario: Same UI element with same event
Scenario: Same UI element with different event
Scenario: UI event triggered but transaction ended
Scenario: Transaction name
Scenario: Transaction name [view.id](http://view.id) or accessibility identifier not specified
The text was updated successfully, but these errors were encountered: