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

Project: Add Sampling Decision to Trace Envelope Header #8

Closed
9 tasks done
cleptric opened this issue Jul 6, 2023 · 3 comments
Closed
9 tasks done

Project: Add Sampling Decision to Trace Envelope Header #8

cleptric opened this issue Jul 6, 2023 · 3 comments

Comments

@cleptric
Copy link
Member

cleptric commented Jul 6, 2023

Project Board

https://github.com/orgs/getsentry/projects/129

Web Frontend SDKs

  1. Feature: Spans Status: Backlog
    AbhiPrasad

Web Backend SDKs

  1. Status: In Progress Type: Improvement
    cleptric
  2. Enhancement
    antonpirker
  3. enhancement
    sl0thentr0py
  4. Status: In Progress Type: Improvement
    cleptric
  5. Platform: Java
    adinauer
  6. Effort: Small Impact: Medium
    jamescrosswell

Mobile SDKs

  1. Platform: Dart enhancement
    buenaflor
  2. Platform: Cocoa Type: Enhancement

Description

from @iambriccardo

Right now the error tagging doesn't support client side sampling, that is, if a trace is sampled out by the head of the trace, this information is not propagated in the trace header (aka dsc). This means that from the perspective of dynamic sampling, we don't know whether the trace has been sampled out on the client and this could lead to false positives.

We would need to fix this by having the client SDKs add the client sampling decision in the dsc that will be attached to the error. This client sampling decision will work similarly to dynamic sampling, that is, if the head is sampled out all the children are sampled out and vice versa.

Client Sampling Decision DSC RFC

@AbhiPrasad
Copy link
Member

To save on bundle size I would like to only add logic that sets sampled on the DSC if there is an active transaction.

@iambriccardo does that seem fine?

@cleptric
Copy link
Member Author

@AbhiPrasad Yep, the same behaviour in PHP, due to other reasons, though 😬

@stephanie-anderson
Copy link
Collaborator

Closing, project is completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants