Draft
Conversation
trieloff
reviewed
Nov 14, 2025
Contributor
trieloff
left a comment
trieloff
left a comment
There was a problem hiding this comment.
You probably don't need a redirectDuration metric.
I'd split the facets into: redirect.type, redirect.source, redirect.count, redirect.duration and use a histogram facet for redirect.duration (similar to loadresource.target)
ramboz
added a commit
to adobe/helix-rum-enhancer
that referenced
this pull request
Jan 21, 2026
## Use Case As a marketer, I want to know how redirects impact my performance scores so that I can avoid undesired redirect chains. ## Problem At the moment, the OpTel Explorer only reports on internal redirects, not external ones. We've seen in customer discussions that external redirects could cause major increases to the TTFB that were hard to detect and debug. ## Solution Leveraging the `PerformanceNavigationTiming` APIs, we can track the time spent on external redirects before we land on the page, and can also estimate the number of redirects accordingly. Technically, the idea is to track the redirect count and time in the `target` for the `redirect` checkpoint: - `<redirectCount>:<redirectTime>` for internal redirects - `<estimatedRedirectCount>~<redirectTime>` for external redirects ## References adobe/helix-website#1011 See background discussion in https://cq-dev.slack.com/archives/C07198KKQ07/p1761333727781429 ## Test URL https://redirect-time-tracking--helix-rum-enhancer--adobe.aem.page/test/fixtures/otsdk-with-banner.html
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provides an updated
redirectfacet that highlights the time lost in redirects and also separates internal vs. external ones.Description
With adobe/helix-rum-enhancer#516, we are introducing a more fine-grained
redirectcheckpoint for which the value will change from1(redirect count) to1:150or2~237(redirect count and redirect time)The goal here is to update the redirect facts to:
Motivation and Context
See discussion in https://cq-dev.slack.com/archives/C07198KKQ07/p1761333727781429
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: