Why no First Input Delay metric for browser monitor?

holst — Thu, 02 Mar 2023 11:08:43 GMT

Im trying to create Core web vitals dashboards for our browser monitors, similar to the ready templates for RUM data.

But, there is no FID metric. I cant understand why, since in documentation for RUM metrics it says:

For Chromium-based browsers, First input delay is measured using Google-provided APIs. For Firefox, Safari, and Internet Explorer 9+, the metric is measured using a Dynatrace implementation that listens for events of type click, mousedown, keydown, or touchstart and calculates the delay from when the RUM JavaScript registers such events to when the events are triggered.

And the Browser monitor is chromium-based, right? So why no FID metric since that is defined as one of the key web vitals metrics? You have even pushed that in your blogs

https://www.dynatrace.com/news/blog/core-web-vitals-practical-metrics-for-optimal-user-experiences/

https://web.dev/vitals/

Re: Why no First Input Delay metric for browser monitor?

ChadTurner — Sat, 20 May 2023 22:27:16 GMT

@holst if this is a required feature for your organization, the best way to get it implemented into the product is to submit an RFE which the PMs will assess and hopefully add to their roadmap.

topic Why no First Input Delay metric for browser monitor? in Synthetic Monitoring

Why no First Input Delay metric for browser monitor?

Re: Why no First Input Delay metric for browser monitor?