Skip to content

Add an FAQ to trace propagation cheat sheet #13528

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
Apr 28, 2025

Conversation

sentrivana
Copy link
Contributor

@sentrivana sentrivana commented Apr 28, 2025

A small clarification on the trace propagation table page in develop docs since this stuff is kinda counter-intuitive.

Direct link to preview: https://develop-docs-git-ivana-pythonadd-faq-to-trace-propagation.sentry.dev/sdk/telemetry/traces/trace-propagation-cheat-sheet/

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

Copy link

vercel bot commented Apr 28, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
develop-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 28, 2025 0:23am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
changelog ⬜️ Ignored (Inspect) Visit Preview Apr 28, 2025 0:23am
sentry-docs ⬜️ Ignored (Inspect) Visit Preview Apr 28, 2025 0:23am

@sentrivana sentrivana changed the title Add an FAQ to trace propagation cheat sheer Add an FAQ to trace propagation cheat sheet Apr 28, 2025
@sentrivana sentrivana merged commit 70f54d6 into master Apr 28, 2025
14 checks passed
@sentrivana sentrivana deleted the ivana/python/add-faq-to-trace-propagation branch April 28, 2025 12:51
codyde added a commit that referenced this pull request Apr 29, 2025
* 'master' of https://github.com/getsentry/sentry-docs:
  fix(native): add another `crashpad` benefit on macOS to the backend tradeoffs (#13535)
  chore(develop): Update frontend router testing guidance (#13538)
  Bump API schema to 1bf27325 (#13537)
  Fix HTTP headers section in data collected for Java and Android SDK (#13530)
  Add "Data Collected" page for Unreal Engine SDK (#13532)
  feat(seer): Update seer docs (#13448)
  Add an FAQ to trace propagation cheat sheet (#13528)
  Remove note about 40M SourceMap Limit (#13499)
  docs(js): Create SvelteKit Quick Start guide (Wizard setup) (#13480)
  add godot and maui to platforms with screenshot (#13493)
@github-actions github-actions bot locked and limited conversation to collaborators May 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants