Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat: implement labelset #463
feat: implement labelset #463
Changes from 1 commit
3cf95a0
860fe6d
51ef29e
3599b53
05d1c63
46110cc
821ad67
ad37bde
dea892c
2a7e093
cfa46e5
bcfda83
9e9fc27
79f1b9f
88e5980
12751f3
cd4d862
167394e
3b240cb
2969570
eca2236
0d1e26d
58717cb
3727d8f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Should the method accept other forms of input as well? e.g. [str],[str] or Dict<str, str>
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.
I would prefer to avoid [str], [str] to avoid having to validate dupes and length mismatches and instead encourage best practices/simplicity, e.g. just pass a dictionary. I believe the type of Labelset is already a dictionary, although maybe we should specify the arg type here as a Record as well to convey that a LabelSet is just
a canonicalized Record
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.
Consider storing the hash value of a label set values in the actual object. This way, you don't have to perform an expensive conversion every single time you get a handle.
EDIT: Actually, I think the whole point of making LabelSet's a first-class API concept is to avoid the repeated expensive canonicalizing.
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.
This leads to the question: should LabelSet objects be canocalized by default, or only when created by
meter.Labels(...)
?Thoughts? @mayurkale22 @xiao-lix
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.
It was my impression that storing the canonicalized/serialized version in the LabelSet object in order to avoid re-computation was one of the primary reasons for their existence.
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.
With labelSetKey, there's no need to have this function.
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.
I removed
sort()
here because per the specs,meter.labels(...)
function is called before calling any instrument function, thus labels passing to any instrument should be already sorted based on keys. I think we should keephashLabelValues
function to map values and the handle that created the certain values. @mayurkale22 WDYT? Also this may create mistake on user's end when user misuses instrument's method without callingmeter.labels(...)
and pass an unsorted labels directly.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.
This is a valid point, I am gonna give another read on specs. Let us know if you have a better solution to handle this.