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.

  1. Provide volume metrix by consumer group

    currently volume metrix is only granual down to event hub level, it's not enough when troubleshooting multi consumer hubs. please provide metrix per consumer group

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow adding metadata/description for Consumer Groups

    Sometimes, we have consumer groups created for a specific purpose, but it is not very clear with the names (as some of them are GUID's) so we end up creating some more and it ends up a mess. Having a description on the consumer group it makes it easier to identify what is what and maybe easier to clean up even if we had information like "test CG delete later" or something. This is an existing feature in a Secret in KeyVaults.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Hide Dedicated Cluster Internal Namespace from Metrics

    Currently, the dedicated cluster picks up the internal monitoring namespace traffic into the aggregated metrics. As this is the only place that the internal workings shows up, it is confusing to see thousands of messages ingress into a cluster with no user defined namespaces or hubs on it.

    The internals should either be hidden and abstracted, or separated out from user metrics.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Clear Dedicated Cluster Metrics on Creation

    Currently, when a new cluster is created, it shows metrics from notably before its creation timestamp which is confusing.

    New clusters should only show metrics related to workloads that occurred on them from their creation time forward.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow Dedicated Clusters to be Deleted on Demand

    Currently, if you deploy a dedicated cluster you have to wait four hours to delete it. If the four hour window is related to the minimum billing period, the cluster should still be able to be deleted (even though you will be billed for it).

    If it's not tied to the billing window, it would be nice to be able to pend the delete until whatever technical systems are ready and then let the system take over, rather than letting it fail.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Event Hub kafka enabled does not allows KSQL client to be connect

    Event Hub kafka enabled does not allows KSQL client to be connect

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support Event Hub GeoDR Alias as a Monitoring-Logging Endpoint

    Geo Recovery DR Aliases are a tool that create a failover group between Primary and Secondary EH Namespaces.

    Also, diagnostic settings can be applied to resources and can be streamed to Event Hubs as an endpoint. However, it is not possible currently to send logs to an Event Hub GeoDR Alias, that would end up in Primary Namespace, and would switch to Secondary namespace if the first is offline. Similar behavior of that of a SQL Failover Group.

    This feature would be ideal and would solve the issue of resources not being able to write to an Event Hub in…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. TLS

    Need to disable TLS 1.0, 1.1 and 3DES from Azure Event hubs, Service bus and relay.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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…

    42 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. how to add customized EnqueuedTimeUtc to event hub message?

    if we want to delay the eventhub message execution in eventhub receiver for some dependency .

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Event Hubs

Categories

Feedback and Knowledge Base