Checkout page data

  • davidecho

    (@davidecho)


    5 months, 4 weeks ago

    Hi there,

    I have Sentry installed correctly on my website, and it seems to be working well.

    However, I’d like to gather data specifically from the checkout page, as this is where we’re experiencing most of the issues. I’d like to track any errors and performance problems on this page, but I’ve noticed that nothing is being logged in Sentry even though orders are successfully coming through since the installation.

    Could you please advise on why this might be happening or how I can ensure Sentry captures data from the checkout page?

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author stayallive

    (@stayallive)

    5 months, 4 weeks ago

    I am assuming since you didn’t specify that you expect traces from the front-end (JavaScript) and not from the PHP side? If so the problem could be two-fold since it looks like the scripts are loaded correctly on at least the checkout page. I see tracesSampleRate: 0.3 this means only 30% of the requests are sampled, so maybe you are getting unlucky. This might be worsened by adblockers that might block sending events to Sentry.

    If you didn’t expect client side performance reports but server side (PHP) there might be other reasons why events are dropped. You can check out the stats page: https://sentry.io/settings/stats/ and checkout the “Spans” category for your project. There is a chance these pages generate so much data the traces are rejected by Sentry. You can try disabling some features from here: https://github.com/stayallive/wp-sentry#wp_sentry_tracing_features-php. You might want to disable transients (both spans and breadcrumbs) and queries which should be the most “busy” and see if traces start to show up for those pages then and try to re-enable one or the other (spans/breadcrumbs) where I think the spans would be the most useful vs breadcrumbs.

    Hopefully some of this helps.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.