Microsoft Azure Event Hub Consumer is a solution to store real-time analytics obtained from almost any provider, enabling more actionable and more informed decisions regarding the future direction of your business. It supports scenarios like:

  • Detecting anomalies
  • Logging the performance of applications to uncover trends
  • Enabling analytics pipelines for actionable decision-making, with clickstreams
  • Dashboarding
  • Archiving data

Transaction processing, user telemetry processing and device telemetry streaming are also major use cases that Azure Event Hub Consumer supports.

Azure Event Hub and Azure IoT Hub are both fully managed services from Microsoft:

  • Azure Event Hub is a data streaming and event ingestion platform that receives and processes event data. Data sent to the event hub can be transformed and stored by using any real-time analytics provider or batching/storage adapters.
  • Azure IoT Hub is a central message hub for bidirectional communication between IoT applications and the devices it manages.

Both services support communication from the devices to the cloud and vice versa.

Why use Azure Event Hub Consumer Telegraf Plugin?

The Azure Event Hub Consumer Telegraf Plugin provides a consumer for use with Azure Event Hub and Azure IoT Hub. This allows you to collect and store all your event data, from your streaming data pipelines and IoT devices, in InfluxDB to help you build scalable applications. Applications that need this type of scale include managing industrial equipment in manufacturing, tracking assets in healthcare, or even monitoring energy consumption of traffic congestion in smart city solutions.

How to use the Event Hub Consumer Telegraf Plugin

If you have signed up for an account with Azure Event Hub and Azure IoT Hub, you can configure this Event Hub Consumer Telegraf plugin to ingest the data into your InfluxDB instance. The default behavior is to create a new Event Hub client from environment variables. This requires one of the following sets of environment variables to be set:

  • Expected Environment Variables:
    • EVENTHUB_NAMESPACE
    • EVENTHUB_NAME
    • EVENTHUB_CONNECTION_STRING
  • Expected Environment Variables:
    • EVENTHUB_NAMESPACE
    • EVENTHUB_NAME
    • EVENTHUB_KEY_NAME
    • EVENTHUB_KEY_VALUE

Default metrics available when using Event Hub Consumer Metrics

The metrics that you collect from your streaming data will depend on the devices that you are monitoring. With this Telegraf plugin, you can assign the metadata collected as either a tag or a field in InfluxDB. By default, all metadata is disabled. The following is a list of the metadata:

  • sequence_number_field = "SequenceNumber"
  • enqueued_time_field = "EnqueuedTime"
  • offset_field = "Offset"
  • partition_id_tag = "PartitionID"
  • partition_key_tag = "PartitionKey"
  • iot_hub_device_connection_id_tag = "IoTHubDeviceConnectionID"
  • iot_hub_auth_generation_id_tag = "IoTHubAuthGenerationID"
  • iot_hub_connection_auth_method_tag = "IoTHubConnectionAuthMethod"
  • iot_hub_connection_module_id_tag = "IoTHubConnectionModuleID"
  • iot_hub_enqueued_time_field = "IoTHubEnqueuedTime"

For more information, please check out the full documentation of the available environment variables.

Project URL   Documentation

Related Resources

AMQP Consumer Telegraf Plugin

Learn how the AMQP Consumer Telegraf Input Plugin receives streaming data from an AMQP message producer.

RabbitMQ Telegraf Plugin

This plugin gathers statistics from your RabbitMQ monitoring cluster. It reads metrics from RabbitMQ servers via the RabbitMQ Management Plugin.

Kafka Telegraf Plugin

Learn how the Kafka Consumer Plugin polls a specified Kafka topic and adds messages to InfluxDB.

Scroll to Top