beats
beats copied to clipboard
Azure Monitor metricset only collect one aggregation type at a time
- Version: 8.13.2
- Operating System: any
- Steps to Reproduce:
A user reported the Azure Monitor metricset is collecting only one aggregation type despite setting up a configuration for three (Maximum, Minimum, Avergate).
The following two configuration variants for Microsoft.EventHub/Namespaces
only return one metric instead of the expected three.
- module: azure
metricsets:
- monitor
enabled: true
period: 60s
client_id: '<redacted>'
client_secret: '<redacted>'
tenant_id: '<redacted>'
subscription_id: '<redacted>'
refresh_list_interval: 600s
resources:
- metrics:
- aggregations:
- Maximum
ignore_unsupported: true
name:
- ActiveConnections
namespace: Microsoft.EventHub/Namespaces
- aggregations:
- Minimum
ignore_unsupported: true
name:
- ActiveConnections
namespace: Microsoft.EventHub/Namespaces
- aggregations:
- Average
ignore_unsupported: true
name:
- ActiveConnections
namespace: Microsoft.EventHub/Namespaces
- module: azure
metricsets:
- monitor
enabled: true
period: 60s
client_id: '<redacted>'
client_secret: '<redacted>'
tenant_id: '<redacted>'
subscription_id: '<redacted>'
refresh_list_interval: 600s
resources:
- metrics:
namespace: Microsoft.EventHub/Namespaces
aggregations:
- Average
- Maximum
- Minimum
ignore_unsupported: true
timegrain: PT1M
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)
I can confirm this is a regression bug introduced in 8.12.
I'm adding the missing tests to ensure the multiple aggregations scenario becomes part of the test suite and we never miss this again.
The fix will be available in the following versions:
- 8.15.0
- 8.14.0
~~I am also backporting it to 8.14.0 and~~ attempting to include it in 8.13.3, but we may not make it in time.