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

💡 Interaction to Next Paint metrics #2233

Closed
wylieconlon opened this issue May 10, 2023 · 11 comments
Closed

💡 Interaction to Next Paint metrics #2233

wylieconlon opened this issue May 10, 2023 · 11 comments
Labels
enhancement New feature or request

Comments

@wylieconlon
Copy link

The Interaction to Next Paint metric is a missing part of the Datadog web vitals tracking. Ideally, it would be tracked automatically.

Describe alternatives you've considered

This can be implemented as a custom metric using a snippet such as this:

import { onINP } from "web-vitals/attribution";

onINP(
  (metric) => {
    return datadogRum.addAction("web-vitals.onINP", {
      ...metric,
      duration: metric.value,
    });
  },
  {
    reportAllChanges: true,
  },
);
@wylieconlon wylieconlon added the enhancement New feature or request label May 10, 2023
@amortemousque
Copy link
Collaborator

Hello @wylieconlon,
Thanks for the feedback. It's on our radar, but hasn't been prioritised yet. We will keep you updated.

@RyanMulready
Copy link

RyanMulready commented Jul 12, 2023

Any update here? We started getting search console warnings about this new metric. Would love to start collecting data in Datadog.

@cy4n
Copy link

cy4n commented Jul 20, 2023

i would also love to see this metric sooner than later.
Google will use the INP metric for their SEO placements from 03/2024, but website providers will need time ahead to actually monitor this metric and fix issues this creates.
(and web vitals monitoring is a major selling point of DD RUM)

per the custom metric the OP stated: as a customer, my main concern using a SaaS service is NOT building stuff myself

@KempfCreative
Copy link

We are starting to prioritize this metric over FID and would appreciate a timeline for implementation. This will be a sticky metric to fix, which is especially dependent on RUM to understand the gaps.

@nhientrandatadog
Copy link

Hi everyone, thanks for your feedback. This has been prioritized for implementation, targeting early Q4 for it to be available in Datadog RUM. Stay tuned for updates.

@cy4n
Copy link

cy4n commented Oct 24, 2023

early Q4 which year? SCNR

@imteekay
Copy link

imteekay commented Oct 24, 2023

Apparently, this was first implemented a couple of months ago #2355 but it was running as an "experiment". After a couple of fixes, I saw a new PR removing this experiment 5 days ago #2448 and it released the change in v5.1.0.

Is it ok to assume that from v5.1.0, we'll have INP being collected automatically on datadog?

Edit: I bumped to the last version and it worked 🎉

@amortemousque
Copy link
Collaborator

Hello everyone,
Yes, the core web vital Interaction To Next Paint (INP) is officially available since v5.1.0!

@ischell
Copy link

ischell commented Oct 25, 2023

This is great to see! I know that when we get this out and see high values, one of the first questions is going to be how to track down the source of the long interactions. Can you share any plans you have around collecting and exposing the recommended INP contextual info referenced here? https://web.dev/articles/find-slow-interactions-in-the-field#what_you_should_collect_in_the_field_and_why

@amortemousque
Copy link
Collaborator

Hello @ischell,
Yes this is something we have in mind and we are currently working on collecting the target element attributed to the Core Web Vitals, including INP.

@amortemousque
Copy link
Collaborator

Hello everyone,
We now collect the Core Web Vital selectors (including the INP selector) since the RUM browser SDK v5.4.0. It is visible in the Datadog UI
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

8 participants