Skip to content
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

POTEL 21 - Drop OpenTelemetry spans for internal Sentry requests #3508

Merged
merged 79 commits into from
Jun 24, 2024

Conversation

adinauer
Copy link
Member

@adinauer adinauer commented Jun 24, 2024

#skip-changelog

📜 Description

Requests to Sentry cause OpenTelemetry auto instrumentation to create spans. We now drop them in SentrySampler using SamplingDecision.DROP.

💡 Motivation and Context

#3499

💚 How did you test it?

📝 Checklist

  • I reviewed the submitted code.
  • 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.
  • 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.

🔮 Next steps

adinauer and others added 30 commits March 27, 2024 16:30
Copy link
Contributor

github-actions bot commented Jun 24, 2024

Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 0c0c76c

Copy link
Contributor

Performance metrics 🚀

  Plain With Sentry Diff
Startup time 334.42 ms 388.60 ms 54.18 ms
Size 1.70 MiB 2.28 MiB 596.92 KiB

Baseline results on branch: feat/potel-20-start-timestamp-sentry-span

Startup times

Revision Plain With Sentry Diff
a5cd4f3 382.74 ms 442.34 ms 59.60 ms

App size

Revision Plain With Sentry Diff
a5cd4f3 1.70 MiB 2.28 MiB 596.92 KiB

if (containsSpotlightUrl(httpUrl, spotlightUrl)) {
return true;
}
// }
Copy link
Collaborator

Choose a reason for hiding this comment

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

Leftover that can be deleted

Copy link
Member Author

Choose a reason for hiding this comment

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

Ideally we reintroduce the if above, then it's needed again. We can retest after doing the alpha release.

@@ -134,51 +129,9 @@ private boolean isSpanTooOld(final @NotNull SpanData span, final @NotNull Sentry
}

private @NotNull List<SpanData> filterOutSentrySpans(final @NotNull Collection<SpanData> spans) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Are there instances where SentrySampler is not invoked and spans need to be filtered here in the exporter?

Copy link
Member Author

Choose a reason for hiding this comment

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

Theoretically it's possible the span is modified during runtime and then has different attributes in SpanExporter.

Base automatically changed from feat/potel-20-start-timestamp-sentry-span to 8.x.x June 24, 2024 12:20
@adinauer adinauer merged commit 407a877 into 8.x.x Jun 24, 2024
2 of 20 checks passed
@adinauer adinauer deleted the feat/potel-21-drop-internal-sentry-spans branch June 24, 2024 12:24
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