[receiver/azuremonitorreceiver] Collect only supported aggregations for each metric (501 not implemented issue)

[celian-garcia]

Description

When we collect metrics, we ask for all available aggregations (Average, Sum, Min, Max, ...) but when we do so with some metrics, Azure API is giving a 501 Not Implemented error. So we need to really respect the definition of each metric.

Link to tracking issue

Relates #43648 (not fully fixing)

Testing

For the full e2e tests, the impact on tests has only been to setup supported aggregation in the metrics definition mocks. We simulate supporting all aggregation in the definition to make sure the tests results are unchanged.

We rely on unit test of the getMetricAggregations function to test a more variety of cases.

Documentation

Updated to provide more details.

[marcinsiennicki95]

Could you explain how the CreateAccount metric will works for Microsoft.DocumentDB/DatabaseAccounts when using an empty [] configuration? The README isn’t clear me: does it automatically collect all available aggregations for this metric (only count), or do I need to specify them explicitly?

[celian-garcia]

Could you explain how the CreateAccount metric will works for Microsoft.DocumentDB/DatabaseAccounts when using an empty [] configuration? The README isn’t clear me: does it automatically collect all available aggregations for this metric (only count), or do I need to specify them explicitly?

I can make it more explicit in the Readme indeed but as long as you define aggregations for one metric of a namespace, you have to define all aggregations for all metrics you want in that namespace. If you want all aggregation of a metric you set a [*] as value.

[marcinsiennicki95]

Thx, now it is clear :) It will work for me, I just want to collect all aggregation for selected metrics.

[celian-garcia]

Thx, now it is clear :) It will work for me, I just want to collect all aggregation for selected metrics.

Ok I will update the README then. Thanks for the early feedback 🙂
I'm not sure [] value will work though. Right value is really the wildcard it's interpreted [*].

Edit: You are right, I'm re-reading the tests and setting value empty [] has the same effect than the wildcard [*]