Is your feature request related to a problem? Please describe.
Currently a pattern which has emerged across the semantic conventions for metrics is that 2 or even 3 of the following metrics are defined
xyz.limit how much of xyz could be usedxyz.level how much of xyz is currently being usedxyz.utilisation the % of xyz which is currently being used
Describe the solution you'd like
As you can see these are all very similar metrics. As such what I would like to see is that when the data points are being aggreated for transmission the limit of the metric is injected into the payload.
This approach would make it easier to visualise metrics as the limit can be plotted against the value, min, max or avg depending on the scenario.
This also reduces data storage as only additional property needs to be stored as opposed to another measurement.
Is your feature request related to a problem? Please describe.
Currently a pattern which has emerged across the semantic conventions for metrics is that 2 or even 3 of the following metrics are defined
xyz.limithow much of xyz could be usedxyz.levelhow much of xyz is currently being usedxyz.utilisationthe % of xyz which is currently being usedDescribe the solution you'd like
As you can see these are all very similar metrics. As such what I would like to see is that when the data points are being aggreated for transmission the limit of the metric is injected into the payload.
This approach would make it easier to visualise metrics as the limit can be plotted against the value, min, max or avg depending on the scenario.
This also reduces data storage as only additional property needs to be stored as opposed to another measurement.