-
Notifications
You must be signed in to change notification settings - Fork 103
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
Configurable web transaction name #475
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Supporting this in starlette would be nice as well. |
Looks like encode/starlette#685 would make this a bit easier. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
bump |
Hi! Thanks for submitting this feature request. Just so I make sure I understand what you are asking for here: You would like the transaction name to be the endpoint name/path instead of the callable name so instead of something like AND You would like this to be configurable via something like Is that correct? |
Sounds correct to me. IIRC, this is how other newrelic agents (java/node) report transaction names OOTB. |
Posting some additional relevant research/info for this feature request: The Java agent optionally supports transaction naming based on endpoint when enable_auto_transaction_naming is set to False. There is a cautionary statement at the bottom of this setting about metric grouping issues. Note, in order to distinguish between the same api endpoint being called with a different method the method is included after the api endpoint path name: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
bump |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
bump |
Hello @billcrook if you would like to submit a PR our team would be happy to review it. This is not currently on our roadmap. |
While I appreciate the opportunity, I must respectfully decline to offer pro-bono services for a publicly-traded company. I'll be exploring other Python-friendly APM options. Thanks. |
I'm using Flask framework, and the web transaction name is automatically determined by callable_name of function.
As a result, stakeholders that access NewRelic dashboards cannot understand which endpoint is related to the transaction.
I would like to have the option to configure the web transaction name according to the rule, which more informative and is known by other stakeholders.
I've considered using
set_transaction_name
but we don't use new relic agent directly in our code, and doing so would not be as clean as having it configured as part of agent initialisation.It's a feature that we must have in order to be able to handle production failures rapidly (currently we have to lookup the relevant function in our code base which wastes precious time)
The text was updated successfully, but these errors were encountered: