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.
When collecting metrics from Microsoft Azure, there's the notion of dimensions. Each dimensions is associated to a list of values.
To get these dimensions as metadata labels, the azuremonitor receiver already collect all available dimensions in the resource definition and put them in the query filter when querying the resource metrics. This allow the query result to be "split" by dimension and thanks to that we can create the metadata labels. Cool!
Problem 1
But. In some cases Azure says that a resource definition allows a dimension and if we put them in the filter, nothing is returned.
Problem 2
Some user may want to completely disable dimensions, if they don't care about it. Or don't want a big cardinality.
Describe the solution you'd like
Problem 1 solution:
As we cannot guess by advance which dimensions is wrongly provided by Azure, we have to let the user fix it by config. Allowing her/him to override the dimensions specified by Azure.
Problem 2 solution:
A simple optout boolean, that will prevent from getting dimensions. With default value to true in order to not introduce breaking change.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
receiver/azuremonitor
Is your feature request related to a problem? Please describe.
When collecting metrics from Microsoft Azure, there's the notion of dimensions. Each dimensions is associated to a list of values.
To get these dimensions as metadata labels, the azuremonitor receiver already collect all available dimensions in the resource definition and put them in the query filter when querying the resource metrics. This allow the query result to be "split" by dimension and thanks to that we can create the metadata labels. Cool!
Problem 1
But. In some cases Azure says that a resource definition allows a dimension and if we put them in the filter, nothing is returned.
Problem 2
Some user may want to completely disable dimensions, if they don't care about it. Or don't want a big cardinality.
Describe the solution you'd like
Problem 1 solution:
As we cannot guess by advance which dimensions is wrongly provided by Azure, we have to let the user fix it by config. Allowing her/him to override the dimensions specified by Azure.
Problem 2 solution:
A simple optout boolean, that will prevent from getting dimensions. With default value to true in order to not introduce breaking change.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: