Skip to content

LCP element span does not correlate with LCP vertical mark in waterfall #13408

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

Closed
3 tasks done
serglom21 opened this issue Aug 16, 2024 · 4 comments
Closed
3 tasks done
Labels
Feature: web-vitals Package: remix Issues related to the Sentry Remix SDK Stale

Comments

@serglom21
Copy link

serglom21 commented Aug 16, 2024

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/remix

SDK Version

8.25.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

Customer Case

Sentry reports the LCP value for a page load and the LCP element that contributed to the value. However, the LCP value for the pageload itself does not match with the end of the span of the LCP element in the waterfall

Expected Result

I would expect the LCP element span to finish at the same timeframe as the reported value of the LCP vital for the page load

Actual Result

The LCP element span finishes way before the time that Sentry reports as the LCP for the pageload

Image

Image

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Aug 16, 2024
@github-actions github-actions bot added the Package: remix Issues related to the Sentry Remix SDK label Aug 16, 2024
@serglom21 serglom21 changed the title LCP element span does not correlate with LCP vertical mark for trace in waterfall LCP element span does not correlate with LCP vertical mark in waterfall Aug 16, 2024
@Lms24
Copy link
Member

Lms24 commented Aug 19, 2024

Backlogging to triage after hackweek

@Lms24
Copy link
Member

Lms24 commented Aug 28, 2024

This might be related to some weird LCP/FCP/FP value normalization code we have in the SDK. I will investigate if we can remove this logic as it's massively screwing up web vital accuracy.

@Lms24
Copy link
Member

Lms24 commented Dec 10, 2024

@serglom21 do you have an update if after updating to a more recent SDK version the problem still persists?

@getsantry getsantry bot moved this to Waiting for: Community in GitHub Issues with 👀 3 Dec 10, 2024
@getsantry
Copy link

getsantry bot commented Jan 1, 2025

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added the Stale label Jan 1, 2025
@getsantry getsantry bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: web-vitals Package: remix Issues related to the Sentry Remix SDK Stale
Projects
Archived in project
Development

No branches or pull requests

2 participants