Skip to content

ref(tracing): Promote ignored span origin APIs - #6427

Open
adinauer wants to merge 2 commits into
9.x.xfrom
ref/promote-ignored-span-origins-v9
Open

adinauer wants to merge 2 commits into
9.x.xfrom
ref/promote-ignored-span-origins-v9

Conversation

@adinauer

Copy link
Copy Markdown
Member

📜 Description

Promote the ignored span origin configuration APIs by removing their experimental designation:

  • SentryOptions.getIgnoredSpanOrigins()
  • SentryOptions.addIgnoredSpanOrigin(...)
  • SentryOptions.setIgnoredSpanOrigins(...)

💡 Motivation and Context

These configuration APIs are ready to be part of the stable public API for the v9 release.

💚 How did you test it?

  • ./gradlew spotlessApply apiDump
  • ./gradlew :sentry:test --tests io.sentry.SentryOptionsTest --tests io.sentry.util.SpanUtilsTest

📝 Checklist

  • I added GH Issue ID & Linear ID
  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.
  • Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

None.

Remove the experimental designation from the ignored span origin configuration APIs for the v9 release.
@adinauer
adinauer marked this pull request as ready for review October 30, 2026 09:33
@sentry

sentry Bot commented Oct 30, 2026

Copy link
Copy Markdown

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.62.0 (1) release

⚙️ sentry-android Build Distribution Settings

* @param ignoredSpanOrigins the list of strings/regex patterns
*/
@ApiStatus.Experimental
public void setIgnoredSpanOrigins(final @Nullable List<String> ignoredSpanOrigins) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it intentional that the getter and setter have different types?
getIgnoredSpanOrigins returns List<FilterString>
setIgnoredSpanOrigins takes List<String>

this makes the API non symetrical and makes the kotlin synthetic accessors half work

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's been this way for a while.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants