Skip to content

docs: Update docs to clarify New Relic browser monitoring auto-insertion limitations - #4128

Open
mrjertop wants to merge 1 commit into
uselagoon:mainfrom
mrjertop:patch-1
Open

docs: Update docs to clarify New Relic browser monitoring auto-insertion limitations#4128
mrjertop wants to merge 1 commit into
uselagoon:mainfrom
mrjertop:patch-1

Conversation

@mrjertop

Copy link
Copy Markdown

General Checklist

  • Affected Issues have been mentioned in the Closing issues section N/A
  • Documentation has been written/updated
  • PR title is ready for inclusion in changelog

Database Migrations

  • If your PR contains a database migation, it MUST be the latest in date order alphabetically N/A

Description

Clarifies that NEWRELIC_BROWSER_MONITORING_ON enables automatic insertion of the New Relic browser monitoring JavaScript, but does not guarantee that auto-instrumentation will succeed in all cases.

New Relic notes that auto-instrumentation does not work when a Content-Length header is set, in which case manual insertion may be required.

Reference: https://docs.newrelic.com/docs/apm/agents/php-agent/features/browser-monitoring-php-agent/

Closing issues

None

Clarify that enabling NEWRELIC_BROWSER_MONITORING_ON only enables automatic JavaScript insertion and does not guarantee successful instrumentation. Note that manual insertion may be required when the application sets a Content-Length header.
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