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.
Right now, when a label is required for a Metric, it is not enforced and potentially corrupted metrics can be sent.
We are testing the output of the metrics but the promotheus library is able to enforce that.
It also enables us to put some constants as labels and create a wrapped metric, which needs fewer labels.
Describe the solution you'd like
Please add to the metrics a generic place for the required labels.
If it is possible to add the "partial labeling of a metric" it would be great!
Describe alternatives you've considered
We are wrapping the creation and access of the built-in metric to enforce the labels in the types.
I think this is an interesting feature. I would suggest experimenting with the type interfaces in @opentelemetry/api-metrics and try not to put a requirement for SDKs to do anything to support it (i.e. enforcing the actual filters).
I think this is an interesting feature. I would suggest experimenting with the type interfaces in @opentelemetry/api-metrics and try not to put a requirement for SDKs to do anything to support it (i.e. enforcing the actual filters).
If the required labels are known by the user creating the metric then maybe this can be accomplished with generics on create{metricType} methods.
Is your feature request related to a problem? Please describe.
Right now, when a label is required for a Metric, it is not enforced and potentially corrupted metrics can be sent.
We are testing the output of the metrics but the promotheus library is able to enforce that.
It also enables us to put some constants as labels and create a wrapped metric, which needs fewer labels.
Describe the solution you'd like
Please add to the metrics a generic place for the required labels.
If it is possible to add the "partial labeling of a metric" it would be great!
Describe alternatives you've considered
We are wrapping the creation and access of the built-in metric to enforce the labels in the types.
Additional context
Here is some code for example:
The text was updated successfully, but these errors were encountered: