-
Notifications
You must be signed in to change notification settings - Fork 772
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
ResourceBuilder API #1533
ResourceBuilder API #1533
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1533 +/- ##
==========================================
- Coverage 80.98% 80.98% -0.01%
==========================================
Files 236 237 +1
Lines 6433 6453 +20
==========================================
+ Hits 5210 5226 +16
- Misses 1223 1227 +4
|
My gut says yes. These seem similar to the SemanticConventions class that we've kept internal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add entry to changelog.md as this is breaking existing APIs.
@cijothomas You see the two use cases in the description? How you feel about that? I thought about removing |
…elemetry-dotnet into resource-create
Changes - V2.5
Switched
Resources
API to use a builder pattern.Resource
implements the specification.ResourceBuilder
can be used to build up a finalResource
fromResource
s orIResourceDetector
s which will be merged together.ResourceBuilder
give user's a friendly API to work with and extension authors something to extend.TracerProviderSdk
now usesResourceBuilder
to do its work.SetResource
is nowSetResourceBuilder
.Resource
semantic conventions internal.Public API Changes
Usage
TODOs
CHANGELOG.md
updated for non-trivial changes