You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Add Ability to pass in multiple Attributes into one otel.instrument() call.
Describe the solution you'd like
What I propose is adding additional signatures to otel.instrument that support attributes in the format of Map<String, Map<String,String>> where the strings represent <Attribute, <LabelKey, LabelValue>>
Example:
currently what is required to collect this metric
@Mrod1598 I can see the use of this feature and think it can be helpful. Wouldn't we want the attributes to map to label functions to keep with the current convention? Otherwise we seem to be limiting the capabilities out of the gate imo.
Is your feature request related to a problem? Please describe.
Add Ability to pass in multiple Attributes into one
otel.instrument()
call.Describe the solution you'd like
What I propose is adding additional signatures to otel.instrument that support attributes in the format of
Map<String, Map<String,String>>
where the strings represent<Attribute, <LabelKey, LabelValue>>
Example:
currently what is required to collect this metric
What it would like with the proposed solution
The text was updated successfully, but these errors were encountered: