New component: Azure Monitor receiver

[altuner]

The purpose and use-cases of the new component

The new receiver would allow to collect Azure Monitor metrics per a subscription/resource group(s) by using Azure REST API.

Example configuration for the component

azure_monitor:
  subscription_id: %SUBSCRIPTION_ID%
  tenant_id: %TENANT_ID%
  client_id: %CLIENT_ID%
  client_secret: %CLIENT_SECRET%
  collection_interval: 60s
  resource_groups: %LIST_OF_RESOURCE_GROUPS%

Telemetry data types supported

Metrics

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.

Sponsor (optional)

No response

Additional context

No response

[atoulme]

Thanks @altuner ! Are you affiliated with the vendor?

[altuner]

@atoulme no affiliation with azure

[codeboten]

I'm happy to sponsor this component @altuner. Just a couple of questions:

subscription_id: %SUBSCRIPTION_ID%

Just confirming here, the % notation is expecting an environment variable? ie. ${env:SUBSCRIPTION_ID}?

resource_groups: %LIST_OF_RESOURCE_GROUPS%

What would the values for resource_groups look like? is it expected to be an array?

[altuner]

@codeboten thanks for accepting.

1. Going to get that from config, but over there it could be received from ENV var
2. What's the preferred option: array or comma separated?

[cartersocha]

It’d be nice to have more granular controls.

As a user I’d like to at least be able to specify which services I’d like metrics from, and if possible control over what specific metrics that service sends. The specific metrics is more of a nice to have.

[ransagy]

Is there a working example of this? Even with debug level telemtry and detailed verbosity on the local logging exporter, i can't ever see this receiver doing anything in my tests. I'm sure this is misconfiguration on my part, but i can't find any info on how this is used or any logs it produces when trying to scrape the azure APIs.