Event Hubs
Azure Event Hubs is a hyper-scale data ingestion service, fully-managed by Microsoft, that enables you to collect, store and process trillions of events from websites, apps, IoT devices, and any stream of data.
-
Allow Secondary EventHub's tags to be updated via ARM/PS/Policies
When setting up Azure policy for tag inheritance, you cannot exclude secondary namespaces, even though by definition the secondary namespaces cannot be updated under any circumstances. So when you do an automated deployment the policy kicks in and deployment fails wit the error "Cannot update a namespace that is secondary".
The only suggested way to get around this from Microsoft is to break the pairing (10 minutes) delete secondary namespace's event hubs (2-5 minutes) and set up tags enable pairing gain (10 minutes). I am setting this as the baseline, and it turns out it will be at least 25…
38 votes -
Built-in Capture feature of Event Hub should preserve milliseconds in EnqueuedTimeUTC system property
When activating the built-in capture feature in Event Hub, messages are stored in Blobs using AVRO format. In AVRO, system prop EnqueuedTimeUTC is serialized as a string, and the odd part is that milliseconds are not there. Basically, capture feature is truncating the original information, which it should not do
4 votes -
Add aliasPrimaryConnectionString to Event Hubs ARM reference() object
Use case: Output from ARM template the primary connection string of an event hub geo-DR alias. Similar to the 'primaryConnectionString' property, but using the alias primary connection string.
For example, "[reference(....).primaryConnectionString]" works for the non-alias connection string, but "[reference(....).aliasPrimaryConnectionString]" doesn't exist.
Here's the error if you try it:
The language expression property 'aliasPrimaryConnectionString' doesn't exist, available properties are 'primaryConnectionString, secondaryConnectionString, primaryKey, secondaryKey, keyName'..
3 votes -
Allow more than 10 hubs per event hub namespace
Event hub namespaces have a hard limit of 10 hubs. It would be great to be able to raise that limit to 100 or 1000 or whatever via a support request.
We use Azure Event Hubs with Kafka. A namespace for us is a kafka server and a hub is a kafka topic. Now we have to split topics per kafka server based on Azure's 10 hubs hard limit, which is counterintuitive and complicates our setup.
87 votes -
Docker image for Event Hub in local/dev/test environments
A container that acts like an event hub so that in local/dev/test/ci environments it's easy to spin up and tear down application stacks that are dependent on event hub.
8 votes -
Provide Event Hub viewer / explorer
It would be good if some sort of viewer/explore was provided for looking at the events within an Event Hub. This could be done either via the portal or Azure Storage Explorer.
When developing I currently use https://marketplace.visualstudio.com/items?itemName=Summer.azure-event-hub-explorer to view events as they are produced.
However, it would be good if a tool existed that let you browse events within the retention period. With the possibility to query by timestamp & partition key. As well as the event body, it would be good to be able to see the properties and other metadata.
We use Event Hub as the integration…
22 votes -
Remove the EventHub Message Size limit of 1MB
Currently we have a size limit on the incoming messages on an EventHub as 1MB. Some processes batch the messages before sending them, to avoid making several POST requests. Even though the batch size is small as 10, the size is unpredictable when the message is sent, as it hits the 1MB mark. Please could we remove the size limit or at least increase the limit form 1MB to 5MB/10MB?
Kafka does not have a size limit. Google has a limit of 10MB.
19 votes -
Kafka protocol prevents connections from closing after a GeoDR failover
Event Hub Disaster Recovery needs manual intervention of restarting the application to start pushing messages to secondary namespace as kafka protocol prevents connections from closing after triggering failover.
It would be nice if the kafka can automatically have a new connection at the time of failover.
1 vote -
Diagnostic setting should allow EventHub SAS policy instead of Namespace SAS policy
In Diagnostic setting for any resource when sending events to EventHub it allows only namespace SAS policy. It will be good if it allows EventhHub SAS Policy.
Also today the option should say “EventHub Namespace policy name” instead of “Event hub policy name” as it confuses many users.
1 vote -
emulator
An Azure Event Hub emulator (preferably in a container) to do local testing
38 votes -
Data Lake Gen2 Capture Support
Currently you can capture to Data Lake Gen1 or Blob but not Data Lake Gen 2. Sad times.
35 votes -
ORC format for Event Capture
Please support ORC format for event capture. Research suggests it could be much denser for sparse data.
FYI: It is already supported by Data Factory, SQL DW/Synapse, ADLA, and Hive (via HDInsight).
1 vote -
Allow Event Capture to output in different file formats
Currently event capture only supports writing in avro. It would be nice to support other file formats for processing e.g JSON and parquet.
3 votes -
Please provide message and events replication for disaster recovery in the Event hub .Currently It supports metadata replication only.
Please provide message and events replication for disaster recovery in the Event hub .Currently It supports metadata replication only.We have to poll stuck messages from old primary event hub.Event hub Disaster recovery involves manual steps .Please provide feature to replicated the messages also .So that this process become automatic.
5 votes -
I want to see number of outgoing messages by consumer group
I can load up graphs showing outgoing messages by the event hub, but I want to see more granularly down to outgoing messages by the consumer group.
24 votes -
event hubs firewall
Provide an option to allow azure services access through the firewall for Azure Event Hubs.
It is common practice to utilize services such as Azure Stream Analytics to consume data from Event Hubs. When enabling the firewall for the event hub service this blocks ASA from connecting. Other services such as ADLS and Azure SQL Database already have this simple option to toggle for their firewall settings. It would be great to have this common option for firewall options across all services.
24 votes -
Kafka Streaming connection with Event Hub
In trying to be more efficient with read/writes into CosmosDB my customer is requesting that having a Kafka Stream connect to Event Hub directly will provide some signficant savings. Also Kafka is very commonly used for Streaming across various enterprises and so hopefully supporting this connectivity for Event Hub might mean a good thing.
Some more details with an example below, there are workarounds I am sure but hope this helps:
o We currently have several read services and several write services. With Kafka Streaming the reads are consolidated in a Kafka queue and published to Event Hub as a…
8 votes -
In azure portal Eventhub how to find AMQP links are idle, expired, active etc.
In azure portal Eventhub how to find AMQP links are idle, expired, active etc.
1 vote -
add a description free text field inside envent hub IP firewall list
add a description free text field inside envent hub IP firewall list
1 vote -
Diagnostics Logging should also log successful/unsuccessful authentication/authorization requests
Same as in Azure Search, Cosmos DB and other components, diagnostics logging should also log 401/403 errors when e.g. trying to access Event Hubs with a wrong Token/Key.
This is important for security reasons to setup e.g. Alerting in Log Analytics to monitor "unsuccessfull authentication/authorization" attempts
8 votes
- Don't see your idea?