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
In Azure monitor metricset, after the metric values are collected from Azure api, the metricdefinition for which the values got fetched, is trying to be matched against the metric definitions stored in a in memory store.
When the metrics are then mapped to events to be published in ES, the dimensions of the metric definition is checked against the dimension of the metric values. If they do not match, then the value added is an empty string which results to a value empty in ES in the respectful dimension field.
In Azure monitor metricset, after the metric values are collected from Azure api, the metricdefinition for which the values got fetched, is trying to be matched against the metric definitions stored in a in memory store.
beats/x-pack/metricbeat/module/azure/client.go
Line 269 in 0b475be
For the matching process,
Aggregations
,Names
,ResourceId
andprevMet.TimeGrain
is compared.beats/x-pack/metricbeat/module/azure/client_utils.go
Line 94 in 04eac62
But there are cases that the metric definitions have all these fields the same but differ in
Dimensions
field.That leads to the following:
beats/x-pack/metricbeat/module/azure/client.go
Line 272 in 0b475be
empty
in ES in the respectful dimension field.beats/x-pack/metricbeat/module/azure/azure.go
Line 139 in 0b475be
beats/x-pack/metricbeat/module/azure/data.go
Line 151 in 0b475be
beats/x-pack/metricbeat/module/azure/data.go
Line 411 in 0b475be
The text was updated successfully, but these errors were encountered: