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

Use service.name resource attribute instead of span name for service … #138

Merged
merged 1 commit into from
Nov 25, 2021

Conversation

anuraaga
Copy link
Contributor

I had misinterpreted the span name being more appropriate, remembering the transformation we do in the collector's xray exporter, but it should indeed by service name when sampling within OTel.

@anuraaga anuraaga requested a review from a team November 24, 2021 05:09
Copy link
Contributor Author

@anuraaga anuraaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that SamplingRuleApplierTest was updated with the new matching semantics. The other tests were just changed to use a different per-span sampling criteria now that span name couldn't be used anymore.

Copy link
Contributor

@willarmiros willarmiros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code changes lgtm, one question about another attribute

@@ -175,7 +175,7 @@ boolean matches(String name, Attributes attributes, Resource resource) {
}

return urlPathMatcher.matches(httpTarget)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about updating this matcher to HTTP URL instead of target? Separate PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah separate PR

@anuraaga anuraaga merged commit 4775be2 into open-telemetry:main Nov 25, 2021
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.

3 participants