Skip to content

Commit eef06ea

Browse files
Merge pull request #176692 from dkamstra/master
Add Event Hub action doc updates
2 parents dff7fe8 + e2c0a44 commit eef06ea

File tree

4 files changed

+24
-7
lines changed

4 files changed

+24
-7
lines changed

articles/azure-monitor/alerts/action-groups-create-resource-manager-template.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: dkamstra
55
services: azure-monitor
66

77
ms.topic: conceptual
8-
ms.date: 02/19/2021
8+
ms.date: 10/18/2021
99
ms.author: dukek
1010
---
1111

@@ -45,7 +45,7 @@ First template, describes how to create a Resource Manager template for an actio
4545
"resources": [
4646
{
4747
"type": "Microsoft.Insights/actionGroups",
48-
"apiVersion": "2019-03-01",
48+
"apiVersion": "2021-09-01",
4949
"name": "[parameters('actionGroupName')]",
5050
"location": "Global",
5151
"properties": {
@@ -87,6 +87,15 @@ First template, describes how to create a Resource Manager template for an actio
8787
"serviceUri": "http://requestb.in/1bq62iu2",
8888
"useCommonAlertSchema": true
8989
}
90+
],
91+
"eventHubReceivers": [
92+
{
93+
"name": "contosoeventhub1",
94+
"subscriptionId": "replace with subscription id GUID",
95+
"eventHubNameSpace": "contosoeventHubNameSpace",
96+
"eventHubName": "contosoeventHub",
97+
"useCommonAlertSchema": true
98+
}
9099
]
91100
}
92101
}
@@ -133,7 +142,7 @@ First template, describes how to create a Resource Manager template for an actio
133142
"resources": [
134143
{
135144
"type": "Microsoft.Insights/actionGroups",
136-
"apiVersion": "2019-03-01",
145+
"apiVersion": "2021-09-01",
137146
"name": "[parameters('actionGroupName')]",
138147
"location": "Global",
139148
"properties": {

articles/azure-monitor/alerts/action-groups.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create and manage action groups in the Azure portal
33
description: Learn how to create and manage action groups in the Azure portal.
44
author: dkamstra
55
ms.topic: conceptual
6-
ms.date: 05/28/2021
6+
ms.date: 10/18/2021
77
ms.author: dukek
88
---
99
# Create and manage action groups in the Azure portal
@@ -45,7 +45,7 @@ Under **Instance details**:
4545

4646
1. Enter a **Display name**. The display name is used in place of a full action group name when notifications are sent using this group.
4747

48-
![The Add action group" dialog box](./media/action-groups/action-group-1-basics.png)
48+
![The "Add action group" dialog box](./media/action-groups/action-group-1-basics.png)
4949

5050

5151
### Configure notifications
@@ -153,6 +153,14 @@ While setting up *Email ARM Role* you need to make sure below 3 conditions are m
153153
> [!NOTE]
154154
> It can take upto **24 hours** for customer to start receiving notifications after they add new ARM Role to their subscription.
155155
156+
### Event Hub (Preview)
157+
> [!NOTE]
158+
> The Event Hub action type is currently in *Preview*. During the preview there may be bugs and disruptions in availability of the functionality.
159+
160+
An Event Hub action publishes notifications to an [Azure Event Hub](~/articles/event-hubs/event-hubs-about.md). You may then subscribe to the alert notification stream from your event receiver.
161+
162+
Currently the Event Hub action may only be defined using an [Azure Resource Manager template](./action-groups-create-resource-manager-template.md).
163+
156164
### Function
157165
Calls an existing HTTP trigger endpoint in [Azure Functions](../../azure-functions/functions-get-started.md). To handle a request, your endpoint must handle the HTTP POST verb.
158166

122 KB
Loading

articles/event-hubs/includes/event-hubs-trusted-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: event-hubs
55
author: spelluru
66
ms.service: event-hubs
77
ms.topic: include
8-
ms.date: 09/29/2021
8+
ms.date: 10/20/2021
99
ms.author: spelluru
1010
ms.custom: "include file"
1111

@@ -17,7 +17,7 @@ When you enable the **Allow trusted Microsoft services to bypass this fir
1717
| Trusted service | Supported usage scenarios |
1818
| --------------- | ------------------------- |
1919
| Azure Event Grid | Allows Azure Event Grid to send events to event hubs in your Event Hubs namespace. You also need to do the following steps: <ul><li>Enable system-assigned identity for a topic or a domain</li><li>Add the identity to the Azure Event Hubs Data Sender role on the Event Hubs namespace</li><li>Then, configure the event subscription that uses an event hub as an endpoint to use the system-assigned identity.</li></ul> <p>For more information, see [Event delivery with a managed identity](../../event-grid/managed-service-identity.md)</p>|
20-
| Azure Monitor (Diagnostic Settings) | Allows Azure Monitor to send diagnostic information to event hubs in your Event Hubs namespace. Azure Monitor can read from the event hub and also write data to the event hub. |
20+
| Azure Monitor (Diagnostic Settings and Action Groups) | Allows Azure Monitor to send diagnostic information and alert notifications to event hubs in your Event Hubs namespace. Azure Monitor can read from the event hub and also write data to the event hub. |
2121
| Azure Stream Analytics | Allows an Azure Stream Analytics job to read data from ([input](../../stream-analytics/stream-analytics-add-inputs.md)) or write data to ([output](../../stream-analytics/event-hubs-output.md)) event hubs in your Event Hubs namespace. <p>**Important**: The Stream Analytics job should be configured to use a **managed identity** to access the event hub. For more information, see [Use managed identities to access Event Hub from an Azure Stream Analytics job (Preview)](../../stream-analytics/event-hubs-managed-identity.md). </p>|
2222
| Azure IoT Hub | Allows IoT Hub to send messages to event hubs in your Event Hub namespace. You also need to do the following steps: <ul><li>Enable system-assigned identity for your IoT hub</li><li>Add the identity to the Azure Event Hubs Data Sender role on the Event Hubs namespace.</li><li>Then, configure the IoT Hub that uses an event hub as a custom endpoint to use the identity-based authentication.</li></ul>
2323
| Azure API Management | <p>The API Management service allows you to send events to an event hub in your Event Hubs namespace.</p> <ul><li>You can trigger custom workflows by sending events to your event hub when an API is invoked by using the [send-request policy](../../api-management/api-management-sample-send-request.md).</li><li>You can also treat an event hub as your backend in an API. For a sample policy, see [Authenticate using a managed identity to access an event hub](https://github.com/Azure/api-management-policy-snippets/blob/master/examples/Authenticate%20using%20Managed%20Identity%20to%20access%20Event%20Hub.xml). You also need to do the following steps:<ol><li>Enable system-assigned identity on the API Management instance. For instructions, see [Use managed identities in Azure API Management](../../api-management/api-management-howto-use-managed-service-identity.md).</li><li>Add the identity to the **Azure Event Hubs Data Sender** role on the Event Hubs namespace</li></ol></li></ul> |

0 commit comments

Comments
 (0)