Skip to content

feat(python): Update tracing troubleshooting for SDK 3.0 #14436

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

Conversation

sentrivana
Copy link
Contributor

@sentrivana sentrivana commented Jul 23, 2025

Created a new copy of the Tracing > Troubleshooting page for the upcoming SDK 3.0 with the following changes:

  • changed set_data to set_attribute

Direct link to preview: https://sentry-docs-git-ivana-pythonupdate-tracing-troubleshooti-83bb43.sentry.dev/platforms/python/tracing/troubleshooting__v3.x

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 Jul 23, 2025

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

Name Status Preview Comments Updated (UTC)
sentry-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 23, 2025 0:21am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
develop-docs ⬜️ Ignored (Inspect) Jul 23, 2025 0:21am

Copy link

codecov bot commented Jul 23, 2025

Bundle Report

Changes will increase total bundle size by 603 bytes (0.0%) ⬆️. This is within the configured threshold ✅

Detailed changes
Bundle name Size Change
sentry-docs-client-array-push 9.84MB -6 bytes (-0.0%) ⬇️
sentry-docs-server-cjs 12.24MB 609 bytes (0.0%) ⬆️

Affected Assets, Files, and Routes:

view changes for bundle: sentry-docs-client-array-push

Assets Changed:

Asset Name Size Change Total Size Change (%)
static/chunks/pages/_app-*.js -3 bytes 880.61kB -0.0%
static/chunks/1831-*.js -3 bytes 423.03kB -0.0%
static/_ezf8ueNIhmTzPDgQFr_N/_buildManifest.js (New) 684 bytes 684 bytes 100.0% 🚀
static/_ezf8ueNIhmTzPDgQFr_N/_ssgManifest.js (New) 77 bytes 77 bytes 100.0% 🚀
static/KsM_DkG9ra1PJ5Is7aPF4/_buildManifest.js (Deleted) -684 bytes 0 bytes -100.0% 🗑️
static/KsM_DkG9ra1PJ5Is7aPF4/_ssgManifest.js (Deleted) -77 bytes 0 bytes -100.0% 🗑️
view changes for bundle: sentry-docs-server-cjs

Assets Changed:

Asset Name Size Change Total Size Change (%)
1729.js -3 bytes 1.75MB -0.0%
../instrumentation.js -3 bytes 1.08MB -0.0%
9523.js -3 bytes 1.05MB -0.0%
../app/[[...path]]/page.js.nft.json 206 bytes 724.79kB 0.03%
../app/platform-redirect/page.js.nft.json 206 bytes 724.71kB 0.03%
../app/sitemap.xml/route.js.nft.json 206 bytes 722.18kB 0.03%

@sentrivana sentrivana marked this pull request as ready for review July 23, 2025 12:26
@sentrivana sentrivana requested review from a team July 23, 2025 12:26
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Bug: URL Construction Error: Double Slashes

The URL construction in the make_request call results in a malformed URL with double slashes. The endpoint variable already starts with a leading slash, but the format string "{base_url}/{endpoint}/" adds an additional slash, creating URLs like https://empowerplant.io//api/0/projects/ep/setup_form/. The format string should be "{base_url}{endpoint}/".

docs/platforms/python/tracing/troubleshooting/index__v3.x.mdx#L86-L91

make_request(
"{base_url}/{endpoint}/".format(
base_url=base_url,
endpoint=endpoint,
),
data=parameters,

Fix in CursorFix in Web


Was this report helpful? Give feedback by reacting with 👍 or 👎

@sentrivana sentrivana merged commit f7b2fd1 into master Jul 25, 2025
13 checks passed
@sentrivana sentrivana deleted the ivana/python/update-tracing-troubleshooting-for-3.x branch July 25, 2025 07:43
lucas-zimerman pushed a commit that referenced this pull request Jul 29, 2025
Created a new copy of the Tracing > Troubleshooting page for the
upcoming SDK 3.0 with the following changes:
- changed `set_data` to `set_attribute`
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.

3 participants