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

Allow client span names to be set based on pattern matching. #46

Merged
merged 1 commit into from
Nov 8, 2014
Merged

Allow client span names to be set based on pattern matching. #46

merged 1 commit into from
Nov 8, 2014

Conversation

joeslice
Copy link
Contributor

@joeslice joeslice commented Nov 4, 2014

For instance, perhaps you want to have your client span names
reported as /api/{userid}/update instead of having span names
that contain all user ids.

For instance, perhaps you want to have your client span names
reported as `/api/{userid}/update` instead of having span names
that contain all user ids.
@kristofa
Copy link
Member

kristofa commented Nov 8, 2014

Thanks for the pull request. This is helpful. Building upon #33.

kristofa added a commit that referenced this pull request Nov 8, 2014
Allow client span names to be set based on pattern matching.
@kristofa kristofa merged commit 15bf78d into openzipkin:master Nov 8, 2014
@joeslice joeslice deleted the pattern-span-name branch November 8, 2014 15:28
@kristofa
Copy link
Member

This pull request is part of brave 2.4 which is just released and should become available through Maven Central in a few hours.

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.

None yet

2 participants