feat(oversight): redirect performance timeline dashboard#1072
Closed
feat(oversight): redirect performance timeline dashboard#1072
Conversation
Add a dedicated redirect performance page (redirectperf.html) showing redirect duration p50/p75 over time, with key metrics and facet-based filtering by redirect type (internal/external) and hop count. Changes: - New RedirectPerfChart class with time-series line chart - New redirectperf.html dashboard page - Add redirectDuration series to slicer.js for all pages - Fix redirect.target facet to show clean hop counts (1, 2, 3) instead of raw encoded values (1~53, 1:54) - Add redirect.type (internal/external) and redirect.count facets when checkpoint=redirect is active - Add redirect.type facet to explorer.html with drilldown to redirectperf.html - Extend updateFilter to accept dynamically registered facets so redirect.type and redirect.count filtering works correctly Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
Commits
|
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
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.
Summary
redirectperf.html) showing redirect duration percentiles (p50/p75) over time as a line chart1,2,3) instead of raw encoded values (1~53,1:54) introduced in feat: track external redirect estimates helix-rum-enhancer#516Details
New files
tools/oversight/redirectperf.html— Dashboard page with standard + redirect-specific key metric cards, Chart.js time-series chart, and redirect facet sidebartools/oversight/charts/redirectperf.js—RedirectPerfChartclass extendingAbstractChart, withgroupBy(time bucketing),defineSeries(hasRedirect, noRedirect, internalRedirect, externalRedirect),updateDataFacets(redirect.type, redirect.count, redirect.source), anddraw(p50/p75 redirect duration per time bucket)Modified files
tools/oversight/slicer.js:redirectDurationseries (extracts duration in ms from redirect checkpoint target)cp === 'redirect'inupdateDataFacetsto overrideredirect.targetwith clean hop counts and registerredirect.type/redirect.countfacetsupdateFilterto accept dynamically registered facets (key in dataChunks.facetFns) so thatredirect.typeandredirect.countfiltering works —isKnownFacet()from rum-distiller uses a static suffix list that doesn't includetypeorcounttools/oversight/explorer.html:redirect.typelist-facet after existingredirect.targetfacetdrilldown="redirectperf.html"to both redirect facetsRedirect checkpoint encoding
The
redirectcheckpoint encodes data in the eventtargetfield:<count>:<duration>for internal redirects (:separator)<estimate>~<duration>for external redirects (~separator)Regex:
/^(\d+)([:~])(\d+)$/Test plan
Tested with
www.cox.com(has both internal and external redirects with 1-60+ hops):Screenshots
Explorer
Deep Dive