Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Starting on 12 March 2024, INP (Interaction to Next Paint) will replace FID (First Input Delay) in our performance score calculation.
Users should update their Sentry SDKs to the latest version (7.104.0+) and enable the INP option to start receiving updated Performance Scores.
Steps to reproduce
Proposed resolution
https://docs.sentry.io/platforms/javascript/performance/instrumentation/...
This requires passing enableInp: true to Sentry.browserTracingIntegration().
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork raven-3432440
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #4
mfbIf there is any downside to enabling INP, such as breaking older versions of self-hosted Sentry server, then we might need to hide this behind a config flag. But, I didn't check for that yet so, keeping this simple for now 🙈
Comment #5
longwaveYeah it's not clear from the docs why you would want to disable this at the moment. Thanks for the swift response - will patch this in on our setup and try it out soon.
Comment #6
mfbIn my testing, enabling this results in a separate ui.interaction.click payload being sent to Sentry; i.e. this is analogous to other JS payload types that we do have settings for, namely, auto session tracking and client reports. So I'd say it's preferable to add a config flag, so if someone doesn't want to be so "chatty" w/ Sentry they can keep it disabled.
Comment #7
mfb...but these extra events weren't actually sent - at least in my testing - until I also updated the JS SDK? So I guess we also need to update that (unless I just had bad luck trying to test this feature)
Comment #10
mfbThis worked in my quick testing, but please re-open if there are any problems