Add Dynatrace RUM monitoring integration - #81
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Integrates Dynatrace Real User Monitoring (RUM) into the application via an agentless JavaScript tag.
Changes
DynatraceRumcomponent that conditionally loads the RUM script based on theNEXT_PUBLIC_DYNATRACE_SCRIPT_URLenvironment variableImplementation details
strategy="beforeInteractive"to ensure monitoring starts as early as possiblenullwhen the environment variable is unset, allowing the feature to be disabled locally and in CI environmentsScriptcomponent withcrossOrigin="anonymous"for proper CORS handlingSetup
Set
NEXT_PUBLIC_DYNATRACE_SCRIPT_URLin Vercel to thesrcURL of the RUM JavaScript tag from the application's agentless monitoring setup in Dynatrace, then redeploy. No API token is required — the tag URL is public by design.