Skip to content

fix: redirect oversight explorer to OpTel oversight#1070

Merged
shsteimer merged 4 commits intomainfrom
redirect-rum-explorer
Apr 9, 2026
Merged

fix: redirect oversight explorer to OpTel oversight#1070
shsteimer merged 4 commits intomainfrom
redirect-rum-explorer

Conversation

@shsteimer
Copy link
Copy Markdown
Collaborator

@shsteimer shsteimer commented Apr 7, 2026

Summary

  • Adds a JS redirect in tools/oversight/explorer.html that sends users to the OpTel oversight explorer
  • Preserves all query parameters
  • Redirect targets vary by environment:
    • www.aem.livehttps://tools.aem.live/tools/optel/oversight/explorer.html
    • *--helix-website--adobe.aem.livehttps://main--helix-tools-website--adobe.aem.live/tools/optel/oversight/explorer.html
    • *--helix-website--adobe.aem.pagehttps://main--helix-tools-website--adobe.aem.page/tools/optel/oversight/explorer.html
  • No redirect on localhost or other domains

Why a code change instead of a content redirect?

This file is served via codebus. Content-based redirects (e.g. via the redirect spreadsheet) don't apply to codebus URLs. The alternatives were a CDN-level redirect or an inline JS redirect. The JS approach is simpler and sufficient here — especially since these files will likely be deleted eventually, at which point we can either drop the redirect entirely or move it to a content redirect if the path has moved to contentbus by then.

Test plan

  • Visit https://redirect-rum-explorer--helix-website--adobe.aem.page/tools/oversight/explorer.html?domain=www.aem.live — should redirect to https://main--helix-tools-website--adobe.aem.page/tools/optel/oversight/explorer.html?domain=www.aem.live
  • Verify all query params carry over
  • Visit on localhost — should not redirect

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

Redirects users landing on /tools/rum/explorer.html to
tools.aem.live/tools/optel/explorer/explorer.html, preserving
query params. Only applies on www.aem.live hostname.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@aem-code-sync
Copy link
Copy Markdown

aem-code-sync Bot commented Apr 7, 2026

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run PSI checks
  • Re-sync branch
Commits

@aem-code-sync
Copy link
Copy Markdown

aem-code-sync Bot commented Apr 7, 2026

On *.aem.page and *.aem.live, redirect to the corresponding
helix-tools-website environment instead of tools.aem.live.
This enables pre-merge testing of the redirect.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@aem-code-sync aem-code-sync Bot temporarily deployed to redirect-rum-explorer April 7, 2026 16:28 Inactive
@shsteimer shsteimer marked this pull request as ready for review April 7, 2026 16:33
@shsteimer shsteimer marked this pull request as draft April 7, 2026 16:33
Move redirect from tools/rum/explorer.html to
tools/oversight/explorer.html, targeting
/tools/optel/oversight/explorer.html on the new tools site.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@aem-code-sync aem-code-sync Bot temporarily deployed to redirect-rum-explorer April 7, 2026 16:38 Inactive
@shsteimer shsteimer changed the title fix: redirect RUM explorer to OpTel explorer fix: redirect oversight explorer to OpTel oversight Apr 7, 2026
@shsteimer shsteimer marked this pull request as ready for review April 7, 2026 16:40
Use regex to detect branch--repo--owner hostname pattern and
rewrite to matching helix-tools-website environment. All other
hostnames (except localhost) redirect to tools.aem.live.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@shsteimer shsteimer merged commit 022c073 into main Apr 9, 2026
6 of 7 checks passed
@shsteimer shsteimer deleted the redirect-rum-explorer branch April 9, 2026 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants