New component: azureservicebusreceiver

[lukasstolt]

The purpose and use-cases of the new component

The purpose of this component is to enable monitoring of Azure Service Bus by collecting metrics such as topic/queue size, count of active messages and count of deadletter messages. Some of these metrics are available using the azuremonitorreceiver, but this way Azure monitor will not be needed. Also, an important addition is that this will enable monitoring of active-/deadletter messages on the scope of a topic subscription, which Azure Monitor does not support.

Example configuration for the component

receivers:  
  azureservicebus:
    namespace_fqdn: example.servicebus.windows.net
    collection_interval: 1m
    auth: default_credentials

Telemetry data types supported

Metrics

Code Owner(s)

@lukasstolt @syron @riha

Sponsor (optional)

No response

Additional context

No response

[atoulme]

Thank you for offering this receiver. This looks interesting to me.

My guess is that your receiver is similar to kafkametrics receiver, in the sense that you connect to the service bus and get metrics from the connection to the service bus without reading messages. Please let me know if this is not a valid guess. If this is indeed the case, that seems like a valid reason to create a new receiver.

[syron]

Exactly, that is the case.

[lukasstolt]

Correct! Here is a POC https://github.com/Integrio/azureservicebusreceiver/

[atoulme]

The next hurdle is to have you become a member of the OpenTelemetry organization to be an official codeowner of this code. You can read about this under https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#membership-levels