Skip to content
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

Change the default newrelic.name_provider #45

Closed
wants to merge 1 commit into from
Closed

Change the default newrelic.name_provider #45

wants to merge 1 commit into from

Conversation

Jalle19
Copy link

@Jalle19 Jalle19 commented Oct 19, 2016

This is a better practice, the previous default was explicitly recommended against in New Relic's documentation:

You have /product/123 and /product/234. If you generate a separate transaction name for each, then New Relic will store separate information for these two transaction names.

Instead, store the transaction as /product/*, or use something significant about the code itself to name the transaction, such as /Product/view. The total number of unique transaction names should be less than 1000. Exceeding that is not recommended.

In MVC frameworks, one good option is to use the newrelic_name_transaction() call where your request is routed and name your transaction with a format of Controller / Action.

Unique values like URLs, Page Titles, Hex Values, Session IDs and uniquely identifiable values should not be used in naming your transactions, but instead tagged to the transaction as a custom parameter. See newrelic_add_custom_parameter() API function.

This is a better practice, the previous default was explicitly recommended against in New Relic's documentation
@Jalle19
Copy link
Author

Jalle19 commented Oct 19, 2016

Fixes #34 too

@Jalle19 Jalle19 closed this Oct 22, 2024
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.

1 participant