-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MongoDB instrumentation is assigning terms directly to segment #74
Comments
Fixed by 4ac4dfc. |
cmcadams-newrelic
pushed a commit
to cmcadams-newrelic/node-newrelic
that referenced
this issue
Jan 29, 2024
…prisma-app/app/semver-and-newrelic-7.5.3 chore(deps): bump semver and newrelic in /prisma-app/app
jsumners-nr
pushed a commit
to jsumners-nr/node-newrelic
that referenced
this issue
Apr 11, 2024
added workflow to prepare release
jsumners-nr
pushed a commit
to jsumners-nr/node-newrelic
that referenced
this issue
Apr 16, 2024
Updated README as part of the repo consistency project
bizob2828
pushed a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 19, 2024
Release v2.0.0
bizob2828
pushed a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 23, 2024
Release v2.0.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
...instead of copying them. This is causing problems because New Relic is contaminating people's search terms, documents, and potentially even indexes. These parameters should be copied instead, and that should only be done if
capture_params
is set.The text was updated successfully, but these errors were encountered: