-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Create structure for Performance content to be common across all platforms #2754
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
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sentry/sentry-docs/itydko4ij/sentry.dev |
@PeloWriter The snippets can be added in this PR, right? So @jennmueng could contribute here? |
Yes, @bruno-garcia - adding here is fine. |
We want to get barebones docs for manual instrumentation out first as everything else is waiting on getsentry/sentry-react-native#1230. Nothing needs to be installed as tracing is already included with the React Native SDK, the configuration would be a little different, and manual instrumentation works exactly the same on react native as on javascript, but maybe a React-component-specific example might be a good addition. So if I understand this correctly I would just add |
Yes, if you populate the directories noted with react-native.mdx files we'll be good to go. |
Note: This PR enables common content for JavaScript (and its guides) as well as React Native. A later PR will enable the common performance content for Go, Python, and PHP.
This is a WIP, the following includes (primarily appropriate code samples) need to be built for React Native:
Getting Started (index.mdx)
Grouping Transactions (group-transactions.mdx)
Manual Instrumentation (manual.mdx)
Retrieve an Active Transaction (retrieve-active-transaction.mdx)
Connecting Frontend and Backend Transactions
no include needed; this is unsupported by React Native at this time
Control Data Truncation (add-to-spans.mdx)
Automatic Instrumentation (automatic.mdx)