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

Support transaction_name_groups and use_path_as_transaction_name #2318

Closed
stevejgordon opened this issue Mar 27, 2024 · 0 comments · Fixed by #2331
Closed

Support transaction_name_groups and use_path_as_transaction_name #2318

stevejgordon opened this issue Mar 27, 2024 · 0 comments · Fixed by #2331
Assignees
Labels
agent-dotnet enhancement New feature or request
Milestone

Comments

@stevejgordon
Copy link
Contributor

I think it makes sense for us to implement transaction_name_groups.

As part of implementing this, we need to consider what our default should be for scenarios such as WCF where the ElasticApmModule should default to $method unknown route and also support: use_path_as_transaction_name to opt into this behavior. This would be a sensitive change to our existing behavior, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent-dotnet enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant