Skip to content

ref(perf): add a feature flag for the new span schema #83532

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

Merged
merged 2 commits into from
Jan 15, 2025

Conversation

mjq
Copy link
Member

@mjq mjq commented Jan 15, 2025

This feature flag will control whether the performance UI uses the new span schema or the legacy one.

Closes https://github.com/getsentry/team-performance/issues/54.

This feature flag will control whether the performance UI uses the new span
schema or the legacy one.
@mjq mjq requested a review from 0Calories January 15, 2025 19:49
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 15, 2025
@mjq mjq merged commit 8ca2fbf into master Jan 15, 2025
49 checks passed
@mjq mjq deleted the mjq-new-span-schema-ff branch January 15, 2025 21:08
andrewshie-sentry pushed a commit that referenced this pull request Jan 22, 2025
This feature flag will control whether the performance UI uses the new
span schema or the legacy one.

Closes getsentry/team-performance#54.
@github-actions github-actions bot locked and limited conversation to collaborators Jan 31, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants