You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-dedicated-cluster-create-portal.md
+19-15Lines changed: 19 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,17 @@
2
2
title: Create an Event Hubs dedicated cluster using the Azure portal
3
3
description: In this quickstart, you learn how to create an Azure Event Hubs cluster using Azure portal.
4
4
ms.topic: quickstart
5
-
ms.date: 06/14/2022
5
+
ms.date: 02/07/2023
6
6
ms.custom: mode-ui
7
7
---
8
8
9
-
# Quickstart: Create a dedicated Event Hubs cluster using Azure portal
10
-
Event Hubs clusters offer single-tenant deployments for customers with the most demanding streaming needs. This offering has a guaranteed 99.99% SLA and is available only on our Dedicated pricing tier. An [Event Hubs cluster](event-hubs-dedicated-overview.md) can ingress millions of events per second with guaranteed capacity and subsecond latency. Namespaces and event hubs created within a cluster include all features of the premium offering and more, but without any ingress limits. The Dedicated offering also includes the popular [Event Hubs Capture](event-hubs-capture-overview.md) feature at no additional cost, allowing you to automatically batch and log data streams to [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md) or [Azure Data Lake Storage Gen 1](../data-lake-store/data-lake-store-overview.md).
9
+
# Quickstart: Create a dedicated Azure Event Hubs cluster using Azure portal
10
+
Event Hubs clusters offer **single-tenant deployments** for customers with the most demanding streaming needs. This offering has a guaranteed **99.99%** SLA, which is available only in our dedicated pricing tier. An [Event Hubs cluster](event-hubs-dedicated-overview.md) can ingress millions of events per second with guaranteed capacity and subsecond latency. Namespaces and event hubs created within a cluster include all features of the premium offering and more, but without any ingress limits. The dedicated offering also includes the popular [Event Hubs Capture](event-hubs-capture-overview.md) feature at no additional cost, allowing you to automatically batch and log data streams to [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md) or [Azure Data Lake Storage Gen 1](../data-lake-store/data-lake-store-overview.md).
11
11
12
-
Dedicated clusters are provisioned and billed by **Capacity Units (CUs)**, a pre-allocated amount of CPU and memory resources. You can purchase 1, 2, 4, 8, 12, 16 or 20 CUs for each cluster. In this quickstart, we'll walk you through creating a 1 CU Event Hubs cluster through the Azure portal.
12
+
Dedicated clusters are provisioned and billed by **capacity units (CUs)**, a pre-allocated amount of CPU and memory resources. You can purchase up to 10 CUs for a cluster in the Azure portal. If you need a cluster larger than 10 CU, you can submit an Azure support request to scale up your cluster after its creation. In this quickstart, we'll walk you through creating a 1 CU Event Hubs cluster through the Azure portal.
13
13
14
14
> [!NOTE]
15
-
> This self-serve experience is currently available in preview on [Azure Portal](https://aka.ms/eventhubsclusterquickstart). If you have any questions about the Dedicated offering, please reach out to the [Event Hubs team](mailto:[email protected]).
15
+
> This [Azure Portal](https://aka.ms/eventhubsclusterquickstart) self-serve experience is currently in **preview**. If you have any questions about the dedicated offering, reach out to the [Event Hubs team](mailto:[email protected]).
16
16
17
17
18
18
## Prerequisites
@@ -24,7 +24,7 @@ To complete this quickstart, make sure that you have:
24
24
-[Created a resource group](../event-hubs/event-hubs-create.md#create-a-resource-group).
25
25
26
26
## Create an Event Hubs Dedicated Cluster
27
-
An Event Hubs cluster provides a unique scoping container in which you can create one or more namespaces. In this Preview phase of the portal self-serve experience, you can create 1 CU clusters in select regions. If you need a cluster larger than 1 CU, you can submit an Azure support request to scale up your cluster after its creation.
27
+
An Event Hubs cluster provides a unique scoping container in which you can create one or more namespaces.
28
28
29
29
> [!WARNING]
30
30
> You won't be able to delete the cluster for at least 4 hours after you create it. Therefore, you will be charged for a minimum 4 hours of usage of the cluster. For more information on pricing, see [Event Hubs - Pricing](https://azure.microsoft.com/pricing/details/event-hubs/).
@@ -37,17 +37,19 @@ To create a cluster in your resource group using the Azure portal, complete the
37
37
1. Enter a **name for the cluster**. The system immediately checks to see if the name is available.
38
38
2. Select the **subscription** in which you want to create the cluster.
39
39
3. Select the **resource group** in which you want to create the cluster.
40
-
1. Select the **Support Scaling** option to create a cluster that you can scale out or scale in yourself. For more information about
41
-
1. Select a **location** for the cluster. If your preferred region is grayed out or it's temporarily out of capacity, you can submit a [support request](#submit-a-support-request) to the Event Hubs team.
40
+
1. Notice that the **Support Scaling** option is set to **Enabled**.
41
+
1. Select a **location** for the cluster. If your preferred region is grayed out or it's temporarily out of capacity. Submit a [support request](#submit-a-support-request) to the Event Hubs team for further assistance.
42
+
1. For **Capacity units**, move the slider to set the number or CUs. The minimum value is 1 and the maximum value is 10.
42
43
1. Select the **Next: Tags** button at the bottom of the page. You may have to wait a few minutes for the system to fully provision the resources.
4. On the **Review + Create** page, review the details, and select **Create**.
49
+
50
+
> [!IMPORTANT]
51
+
> You won't be able to delete the cluster for at least 4 hours after you create it. Therefore, you will be charged for a minimum 4 hours of usage of the cluster. For more information on pricing, see [Event Hubs - Pricing](https://azure.microsoft.com/pricing/details/event-hubs/).
52
+
1. On the **Review + Create** page, review the details, and select **Create**.
5. After the creation is successful, select **Go to resource** to navigate to the home page for your Event Hubs cluster.
@@ -79,12 +81,12 @@ For clusters created with the **Support Scaling** option set, use the following
79
81
1. Use the slider to increase (scale out) or decrease (scale in) capacity units assigned to the cluster.
80
82
1. Then, select **Save** on the command bar.
81
83
82
-
The **Scale** tab is available only for the Event Hubs clusters created with the **Support scaling** option checked. You don't see the **Scale** tab for clusters that were created before this feature was released or for the clusters you created without selecting the **Support scaling** option. If you wish to change the size of a cluster that you can't scale yourself, or if your preferred region isn't available, submit a support request by using the following steps.
84
+
The **Scale** tab is available only for the Event Hubs clusters created with the **Support scaling** option checked. You don't see the **Scale** tab for clusters that were created before this feature was released or for the clusters you created without selecting the **Support scaling** option. If you wish to change the size of a cluster that you can't scale yourself, or if your preferred region isn't available, submit a support request by using the following steps.
83
85
84
86
### Submit a support request
85
87
86
88
1. In [Azure portal](https://portal.azure.com), select **Help + support** from the left menu.
87
-
2. Select **+ New support request**from the Support menu.
89
+
2. Select **Create a support request**on the toolbar.
88
90
3. On the support page, follow these steps:
89
91
1. For **Issue Type**, select **Technical** from the drop-down list.
90
92
2. For **Subscription**, select your subscription.
@@ -100,10 +102,12 @@ The **Scale** tab is available only for the Event Hubs clusters created with the
100
102
101
103
## Delete a dedicated cluster
102
104
103
-
1. To delete the cluster, select **Delete** from the top menu.
105
+
1. To delete the cluster, select **Delete** from the toolbar on the **Event Hubs Cluster** page for your cluster.
104
106
105
107
> [!IMPORTANT]
106
-
> You won't be able to delete the cluster for at least 4 hours after you create it. Therefore, you will be charged for a minimum 4 hours of usage of the cluster. For more information on pricing, see [Event Hubs - Pricing](https://azure.microsoft.com/pricing/details/event-hubs/).
108
+
> You won't be able to delete the cluster for at least 4 hours after you create it. Therefore, you will be charged for a minimum 4 hours of usage of the cluster. For more information on pricing, see [Event Hubs - Pricing](https://azure.microsoft.com/pricing/details/event-hubs/).
109
+
110
+
:::image type="content" source="./media/event-hubs-dedicated-cluster-create-portal/delete-menu.png" alt-text="Screenshot showing the Delete button on the Event Hubs Cluster page.":::
107
111
1. A message will appear confirming your wish to delete the cluster.
108
112
1. Type the **name of the cluster** and select **Delete** to delete the cluster.
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-dedicated-overview.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,16 @@
2
2
title: Overview of Azure Event Hubs dedicated tier
3
3
description: This article provides an overview of dedicated Azure Event Hubs, which offers single-tenant deployments of event hubs.
4
4
ms.topic: article
5
-
ms.date: 06/29/2022
5
+
ms.date: 02/07/2023
6
6
---
7
7
8
8
# Overview of Azure Event Hubs dedicated tier
9
9
10
-
*Event Hubs clusters* offer **single-tenant**deployments for customers with the most demanding streaming needs. This single-tenant offering has a guaranteed 99.99% SLA and is available only on our dedicated pricing tier. An Event Hubs cluster can ingress millions of events per second with guaranteed capacity and subsecond latency. Namespaces and event hubs created within the dedicated cluster include all features of the premium offering and more, but without any ingress limits. It also includes the popular [Event Hubs Capture](event-hubs-capture-overview.md) feature at no additional cost. The Event Hubs Capture feature allows you to automatically batch and log data streams to Azure Storage or Azure Data Lake Storage.
10
+
Event Hubs clusters offer **single-tenant deployments** for customers with the most demanding streaming needs. This offering has a guaranteed **99.99%** SLA, which is available only in our dedicated pricing tier. An [Event Hubs cluster](event-hubs-dedicated-overview.md) can ingress millions of events per second with guaranteed capacity and subsecond latency. Namespaces and event hubs created within a cluster include all features of the premium offering and more, but without any ingress limits. The dedicated offering also includes the popular [Event Hubs Capture](event-hubs-capture-overview.md) feature at no additional cost, allowing you to automatically batch and log data streams to [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md) or [Azure Data Lake Storage Gen 1](../data-lake-store/data-lake-store-overview.md).
11
11
12
-
Clusters are provisioned and billed by **capacity units (CUs)**, a pre-allocated amount of CPU and memory resources. You can purchase 1, 2, 4, 8, 12, 16 or 20 CUs for each cluster. How much you can ingest and stream per CU depends on various factors, such as the following ones:
12
+
Dedicated clusters are provisioned and billed by **capacity units (CUs)**, a pre-allocated amount of CPU and memory resources. You can purchase up to 10 CUs for a cluster in the Azure portal. If you need a cluster larger than 10 CU, you can submit an Azure support request to scale up your cluster after its creation.
13
+
14
+
How much you can ingest and stream per CU depends on various factors, such as the following ones:
13
15
14
16
- Number of producers and consumers
15
17
- Payload shape
@@ -19,7 +21,7 @@ Clusters are provisioned and billed by **capacity units (CUs)**, a pre-allocated
19
21
> All Event Hubs clusters are Kafka-enabled by default and support Kafka endpoints that can be used by your existing Kafka based applications. Having Kafka enabled on your cluster does not affect your non-Kafka use cases. There is no option or need to disable Kafka on a cluster.
20
22
21
23
## Why dedicated tier?
22
-
The dedicated tier of Event Hubs offers three compelling benefits for customers who need enterprise-level capacity:
24
+
The dedicated tier of Event Hubs offers three compelling benefits to customers who need enterprise-level capacity:
23
25
24
26
### Single-tenancy guarantees capacity for better performance
25
27
A dedicated cluster guarantees capacity at full scale. It can ingress up to gigabytes of streaming data with fully durable storage and subsecond latency to accommodate any burst in traffic.
Copy file name to clipboardExpand all lines: articles/event-hubs/includes/event-hubs-dedicated-clusters-faq.md
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: event-hubs
5
5
author: spelluru
6
6
ms.service: event-hubs
7
7
ms.topic: include
8
-
ms.date: 06/14/2022
8
+
ms.date: 02/07/2023
9
9
ms.author: spelluru
10
10
ms.custom: "include file"
11
11
@@ -23,19 +23,19 @@ The following table shows the benchmark results that we achieved during our test
23
23
| Batches of 10x10KB | 2 | 666 MB/sec | 66.6k messages/sec | 1.33 GB/sec | 133k messages/sec | 666 TUs | 166 TUs |
24
24
| Batches of 6x32KB | 1 | 1.05 GB/sec | 34k messages / sec | 1.05 GB/sec | 34k messages/sec | 1000 TUs | 250 TUs |
25
25
26
-
In the testing, the following criteria was used:
26
+
In the testing, the following criteria were used:
27
27
28
28
- A dedicated-tier Event Hubs cluster with 4 capacity units (CUs) was used.
29
29
- The event hub used for ingestion had 200 partitions.
30
30
- The data that was ingested was received by two receiver applications receiving from all partitions.
31
31
32
32
### Can I scale up/down my cluster?
33
-
If you created the cluster with the **Support Scaling** option set, you can use the [self-serve experience](../event-hubs-dedicated-cluster-create-portal.md#scale-event-hubs-dedicated-cluster), to scale out and scale in as needed. You can scale up to 10 CUs with self-serve scalable clusters. As self-serve scalable dedicated clusters are based out of new infrastructure, they are bound to be performant over dedicated clusters that don't support self-serve scaling. As the performance of dedicated clusters depends on various factors such as resource allocation, number of partitions, storage, and so on, we recommend you to determine the required number of CUs after testing with a real workload.
33
+
If you created the cluster with the **Support Scaling** option set, you can use the [self-serve experience](../event-hubs-dedicated-cluster-create-portal.md#scale-event-hubs-dedicated-cluster) to scale out and scale in as needed. You can scale up to 10 CUs with self-serve scalable clusters. As self-serve scalable dedicated clusters are based out of new infrastructure, they are bound to be performant over dedicated clusters that don't support self-serve scaling. As the performance of dedicated clusters depends on various factors such as resource allocation, number of partitions, storage, and so on, we recommend you to determine the required number of CUs after testing with a real workload.
34
34
35
35
[Submit a support request](../event-hubs-dedicated-cluster-create-portal.md#submit-a-support-request) in the following scenarios to scale out or scale in your dedicated cluster.
36
36
37
37
- You need more than 10 CUs for a self-serve scalable dedicated cluster (a cluster that was created with the **Support scaling** option set).
38
-
- You need to scale out or scale in a cluster that was created without selecting the **Support scaling** option
38
+
- You need to scale out or scale in a cluster that was created without selecting the **Support scaling** option
39
39
- You need to scale out or scale in a dedicated cluster that was created before the self-serve experience was released
40
40
41
41
@@ -51,15 +51,16 @@ Due to difference in the backend architecture, we don't currently support migrat
51
51
CPU consumption is the key indicator of the resource consumption of your dedicated cluster. When the overall CPU consumption is reaching 70% (without observing any abnormal conditions such as high number of server errors or low successful requests), that means your cluster is moving towards its maximum capacity. Therefore you can use this as an indicator to consider whether you need to scale up your dedicated cluster or not.
52
52
53
53
To monitor the CPU usage of the dedicated cluster, you need to follow these steps.
54
-
- In the metrics page of your Event Hubs Dedicated cluster, add a new metric in the Event Hubs as shown below.
55
-
:::image type="content" source="./media/event-hubs-dedicated-clusters-faq/monitoring-dedicated-cluster.png" alt-text="Dedicated cluster CPU consumption metric" lightbox="./media/event-hubs-dedicated-clusters-faq/monitoring-dedicated-cluster.png":::
54
+
- In the metrics page of your Event Hubs Dedicated cluster, select **Add metric**.
55
+
- Select `CPU` as the metric and use the `Max` as the aggregation.
56
56
57
+
:::image type="content" source="./media/event-hubs-dedicated-clusters-faq/metrics-cpu-max.png" alt-text="Screenshot showing the Metrics page with the CPU metric." lightbox="./media/event-hubs-dedicated-clusters-faq/metrics-cpu-max.png":::
58
+
- Then, select **Add filter**, and add a filter for the property type `Role`, use the equal operator and select all three values(`Backend`, `Gateway`) from the dropdown.
57
59
58
-
- Select `CPU` as the metrics and use the `Max` as the aggregation.
59
-
- Then add a filter for the property type `Role`, use the equal operator and select all three values(`SBSAdmin`, `SBSFE`, `SBSEH`) from the dropdown.
60
+
:::image type="content" source="./media/event-hubs-dedicated-clusters-faq/monitoring-dedicated-cluster.png" alt-text="Screeshot showing the metrics page with CPU consumption metric and roles." lightbox="./media/event-hubs-dedicated-clusters-faq/monitoring-dedicated-cluster.png":::
60
61
61
-
Then you can monitor this metric to determine when you should scale your dedicated cluster.
62
-
You can also set up [alerts](../../azure-monitor/alerts/alerts-overview.md) against this metric to get notified when CPU usage reaches the thresholds you set.
62
+
63
+
Then you can monitor this metric to determine when you should scale your dedicated cluster. You can also set up [alerts](../../azure-monitor/alerts/alerts-overview.md) against this metric to get notified when CPU usage reaches the thresholds you set.
0 commit comments