🔊[RUM-2324] Telemetry on other wrong LCP cases

[bcaudan]

Motivation

Following #2515, some LCP data seemed wrong for other reasons than startTime = 0.

Changes

• collect debug logs for LCP with startTime < previous LCP
• collect debug logs for LCP with size < previous LCP
• remove some debug data:
  • visibilityState: always visible
  • prerendering: always false
  • navigationStart: from one case, the value did not really make sense (~30s after timeOrigin) but not sure how reliable it is supposed to be anyway.
• add lcpEntries to the debug data, to double check if the implementation difference with google may have an impact

Testing

• Local
• Staging
• Unit
• End to end

---

I have gone over the contributing documentation.

[bcaudan]

/to-staging

[dd-devflow]

🚂 Branch Integration: starting soon, merge in < 3s

Commit c1c27add40 will soon be integrated into staging-50.

This build is going to start soon! (estimated merge in less than 3s)

you can cancel this operation by commenting your pull request with /to-staging -c!

[dd-devflow]

🚂 Branch Integration: This commit was successfully integrated

Commit c1c27add40 has been merged into staging-50 in merge commit cdc81f9e5d.

Check out the triggered pipeline on Gitlab 🦊

[amortemousque]

/to-staging

[dd-devflow]

🚂 Branch Integration: starting soon, merge in < 0s

Commit c1c27add40 will soon be integrated into staging-51.

This build is going to start soon! (estimated merge in less than 0s)

you can cancel this operation by commenting your pull request with /to-staging -c!

[dd-devflow]

🚂 Branch Integration: This commit was successfully integrated

Commit c1c27add40 has been merged into staging-51 in merge commit 1ccefed72d.

Check out the triggered pipeline on Gitlab 🦊