feat(rust): add getting started docs for tracing #14578
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
![seer-by-sentry[bot]](https://avatars.githubusercontent.com/in/801464?s=60&v=4){kind=small}
Bundle ReportChanges will increase total bundle size by 8.63kB (0.04%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
Files in
App Routes Affected:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
Files in
|
lcian
force-pushed
the
lcian/feat/rust-tracing-docs
branch
from
057ab7a to
de9699d
Compare
| @@ -0,0 +1,120 @@ | |||
| --- | |||
| title: tracing | |||
There was a problem hiding this comment.
I'm a little concerned that this could cause confusion since we also have our own 'Tracing' product. I think it's possible search might send people looking for /platforms/rust/tracing/ to this page or vice-versa. Would it make sense to update the title to something like 'tracing by tokio'? Or maybe add a little notification explaining that this is not about Sentry Tracing?
There was a problem hiding this comment.
/platforms/rust/tracing/ links to /platforms/rust/tracing/instrumentation/automatic-instrumentation/ here:
Do we also want to link to this new guide?
Also should /platforms/rust/tracing/instrumentation/automatic-instrumentation/ link to the guide too?
Do we want to include "Tokio" in the name of the guide? From what I understand the tracing crate and tokio:tracing aren't the same thing. Not sure if all rust devs know the difference. I'm a bit confused on the differences and what they have in common.
| } | ||
| ``` | ||
|
|
||
| By default, error level events are captured as Sentry events, while anything at or above info is added as a breadcrumb. |
There was a problem hiding this comment.
I think we should be explicit when talking about Tokio and Sentry events, even if it's arguably clear from context.
| By default, error level events are captured as Sentry events, while anything at or above info is added as a breadcrumb. | |
| By default, error level events from Tokio are captured as Sentry events, while anything at or above info is added as a breadcrumb. |
|
|
||
| {/* ___PRODUCT_OPTION_START___ logs */} | ||
|
|
||
| To capture structured logs for `tracing` events instead, you need to set up the Sentry layer with a custom event filter that maps to logs, like so: |
There was a problem hiding this comment.
| To capture structured logs for `tracing` events instead, you need to set up the Sentry layer with a custom event filter that maps to logs, like so: | |
| To capture structured logs for Tokio `tracing` events instead, you need to set up the Sentry layer with a custom event filter that maps to logs, like so: |
Adds getting started docs for the
tracingintegration.This is our most popular integration, so we want to have a dedicated page to give it even more visibility.
Currently the only docs we have for this are here which means they're hard to find, and they only document the tracing functionality.