/
Automatically add event hubs
Automatically add event hubs
Scope
The event hub auto-discovery feature enumerates a namespace and resource group for all available event hubs and optionally create consumer groups (if the configuration specifies a consumer group other than $Default
and that consumer group does not exist when the collector connects to the event hub).
OAuth credentials and the Azure Event Hubs Namespace Data Owner role are required.
Process
In the Cloud Collector App, create an Azure Collector instance using this parameters template, replacing the values enclosed in < >
. The region name for each event hub will be logged in the region field of cloud.azure. It is not required to be your Azure region.
{
"inputs": {
"azure_event_hub": {
"credentials": {
"client_id": "<CLIENT ID>",
"client_secret": "<SECRET>",
"subscription_id": "<SUBSCRIPTION>",
"tenant_id": "<TENANT>"
},
"enabled": true,
"id": "<UNIQUE ID>",
"services": {
"event_hubs": {
"queues": {
"<REGION>": {
"event_hub_name": "<HUB NAME>",
"namespace": "<NAMESPACE>"
}
}
},
"event_hubs_auto_discover": {
"resource_group": "<RESOURCE GROUP>",
"namespace": "<NAMESPACE>",
"consumer_group": "devo_autodiscover"
}
}
}
}
}
The consumer group must not be used by any entity other than the collector.
, multiple selections available,
Related content
Automatically add event hubs
Automatically add event hubs
More like this
Manually send an event to Devo with an event hub
Manually send an event to Devo with an event hub
Read with this
Scaling the Event Hub collector
Scaling the Event Hub collector
Read with this
Manual tagging of Event Hub data
Manual tagging of Event Hub data
More like this
Manual tagging of Event Hub data
Manual tagging of Event Hub data
More like this
Azure Event Hub collector
Azure Event Hub collector
More like this