Distrubited Tracing Tutorial #11518
Merged
Distrubited Tracing Tutorial #11518
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Bundle ReportChanges will increase total bundle size by 2.02kB (0.01%) ⬆️. This is within the configured threshold ✅ Detailed changes
|
lizokm
approved these changes
Oct 24, 2024
docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx
Outdated
Show resolved
Hide resolved
docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-backend.mdx
Outdated
Show resolved
Hide resolved
docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-backend.mdx
Outdated
Show resolved
Hide resolved
docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx
Outdated
Show resolved
Hide resolved
docs/product/sentry-basics/distributed-tracing/generate-first-error.mdx
Outdated
Show resolved
Hide resolved
docs/product/sentry-basics/distributed-tracing/generate-first-error.mdx
Outdated
Show resolved
Hide resolved
Comment on lines
44
to
46
| 1. Go back to the browser window and try clicking on the **Nonfat Water** button again, you will no longer see the expected product information. Instead, you'll see text saying something went wrong. If you look at line 88 of the `App.js` file in the `tracing-tutorial-frontend` repo, you'll see this is what the frontend displays when it's call to the backend doesn't return any data. | ||
|
|
||
| 1. Open the terminal window that's running the `tracing-tutorial-backend` server. Here, you'll see that a log letting you know that an error has occurred. |
There was a problem hiding this comment.
Suggested change
| 1. Go back to the browser window and try clicking on the **Nonfat Water** button again, you will no longer see the expected product information. Instead, you'll see text saying something went wrong. If you look at line 88 of the `App.js` file in the `tracing-tutorial-frontend` repo, you'll see this is what the frontend displays when it's call to the backend doesn't return any data. | |
| 1. Open the terminal window that's running the `tracing-tutorial-backend` server. Here, you'll see that a log letting you know that an error has occurred. | |
| 1. Go back to the browser window and click the **Nonfat Water** button again. Instead of seeing the expected product information, you'll now see text telling you that something went wrong. If you look at line 88 of the `App.js` file in the `tracing-tutorial-frontend` repo, you'll see this is what the frontend displays when its call to the backend doesn't return any data. | |
| 1. Open the terminal window that's running the `tracing-tutorial-backend` server. You'll see a log letting you know that an error has occurred. |
docs/product/sentry-basics/distributed-tracing/generate-first-error.mdx
Outdated
Show resolved
Hide resolved
docs/product/sentry-basics/distributed-tracing/generate-first-error.mdx
Outdated
Show resolved
Hide resolved
docs/product/sentry-basics/distributed-tracing/generate-first-error.mdx
Outdated
Show resolved
Hide resolved
…ry-sdk-frontend.mdx Co-authored-by: Liza Mock <[email protected]>
…ry-sdk-backend.mdx Co-authored-by: Liza Mock <[email protected]>
…ry-sdk-backend.mdx Co-authored-by: Liza Mock <[email protected]>
…ry-sdk-frontend.mdx Co-authored-by: Liza Mock <[email protected]>
…error.mdx Co-authored-by: Liza Mock <[email protected]>
…error.mdx Co-authored-by: Liza Mock <[email protected]>
…error.mdx Co-authored-by: Liza Mock <[email protected]>
…error.mdx Co-authored-by: Liza Mock <[email protected]>
…error.mdx Co-authored-by: Liza Mock <[email protected]>
* Make tech stack clearer earlier in text * Split long paragraph * Remove text that probably makes no sense if you are a first time user * Explain DSN in context of the screen a user is currently on * It is clearer in one sentence * Put instructions in corre t order * Move comment * Add new bullet point for importing instrument into server.js * Looks clearer as a diff * Depending on user preferences in their IDE, this might not be line 88, e.g. line length settings * Fix typo
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…through
DESCRIBE YOUR PR
A new interactive tutorial to get set up with Sentry and distributed tracing.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
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