Skip to content
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

[Ready for review] V0 initial improvements to performance data for demo #10

Conversation

cstavitsky
Copy link
Contributor

@cstavitsky cstavitsky commented Nov 1, 2021

  • Enrich performance data for mobile demo (note: does not include react.update spans -- working on that separately)
  • Once we have performance data automated at scale, we will be able to show customers richer and more realistic transactions and spans.
  • The other PR is WIP and contains attempts to get react.update spans showing. The plan is to move forward with what we have now (screenshot below) and then add react.update spans once we figure that out.

Screen Shot 2021-11-01 at 3 30 10 PM

@@ -13,5 +13,13 @@ module.exports = {
inlineRequires: true,
},
}),
minifierConfig: {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This exists so that we don't get profiled components showing up as unknown in spans.

Copy link
Contributor

Choose a reason for hiding this comment

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

nice fix!

@cstavitsky cstavitsky force-pushed the v0_initial_improvements_to_performance_data_for_demo branch from 1e6beca to 4d70c72 Compare November 4, 2021 16:50
@@ -171,6 +171,9 @@ const ProductItem = (props: {
imgcropped: string;
appDispatch: AppDispatch;
}): React.ReactElement => {
React.useEffect(() => {
fetch(`${BACKEND_URL}/success`) // exists just to add span data to demo
Copy link
Contributor

Choose a reason for hiding this comment

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

nice usage and comment

/* You could wrap this with the Sentry Profiler,
* but then you'd have hundreds/thousands of spans because the tools response is not paginated.
*/
const ProfiledImage = Sentry.withProfiler(Image);
Copy link
Contributor

Choose a reason for hiding this comment

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

This helps me remember the Profiler was used, as I go through the rest of this file. Sweet.

@thinkocapo thinkocapo merged commit 50122d4 into sentry-demos:master Nov 11, 2021
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.

2 participants