New Relic APM and Browser correlation for pre-optimization bottleneck measurement
Measuring a bottleneck before optimization requires comparing server-side latency from New Relic APM with client-side timing from New Relic Browser across the integration boundary. The goal is to attribute delay to backend transactions versus rendering and network time in the browser for a given user flow. Correlation depends on distributed tracing linking a
newrelic