Azure Monitor : Metric Receiver(REST Client)

[rajim17]

The purpose and use-cases of the new component

This component is to collect metrics from Azure Monitor platform and parse into OTLP metric format. Azure Monitor provides OS/CPU and major resource level metrics users are interested. List of metrics supported by Azure Monitor can be found here.

Component also provides a way to configure interested metric namespaces to collect.

Example configuration for the component

receivers:
    azuremetric/5_min:
        subscription_id: <azure_subscription_1> // (mandatory) Azure subscription ID
        collection_interval:300
        timegrain: <1M> //  ( optional: default 1M ) fetch 1 min interval metrics for the past 5 mins
        metric_providers: // metric namespace of the resource providers 
            - microsoft.analysisservices/servers
            - microsoft.apimanagement/service                       
            - microsoft.cdn/profiles                                 
            - microsoft.storage/storageaccounts                     
            - microsoft.network/networksecuritygroups               
            - microsoft.network/privatednszones/virtualnetworklinks 
            - microsoft.network/routetables                         
            - microsoft.dbformysql/servers                          
            - microsoft.cache/redis                                 
            - microsoft.compute/virtualmachines                     
            - microsoft.compute/virtualmachinescalesets             
            - microsoft.streamanalytics/streamingjobs 

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

• Azure MetricReceiver will use http client using azure-sdk/azquery module.
• Component can dynamically query all the resources under the subscription and fetch metrics for configured metric namespaces for those resources.
• It also groups multiple metric names and dimensions to reduce number of metric requests to Azure platform.

[nslaughter]

Thank you for opening this, @rajim17. It sounds very similar to issue #18899 which has an open PR in #18898. Could it potentially help with your use case if you provide review on that PR and/or improve the specification in the issue?

[rajim17]

@nslaughter Thanks for pointing out. I should be able to contribute. I will review and add my comments

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.