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-grid/edge/monitor-topics-subscriptions.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Configure the module to emit metrics by setting the `metrics__reporterType` envi
35
35
}
36
36
```
37
37
38
-
Metrics will be available at `5888/metrics` of the module for http and `4438/metrics` for https. For example, `http://<modulename>:4438/metrics?api-version=2019-01-01-preview` for http. At this point, a metrics module can poll the endpoint to collect metrics as in this [example architecture](https://github.com/veyalla/ehm).
38
+
Metrics will be available at `5888/metrics` of the module for http and `4438/metrics` for https. For example, `http://<modulename>:5888/metrics?api-version=2019-01-01-preview` for http. At this point, a metrics module can poll the endpoint to collect metrics as in this [example architecture](https://github.com/veyalla/ehm).
39
39
40
40
## Available metrics
41
41
@@ -57,10 +57,10 @@ Both topics and event subscriptions emit metrics to give you insights into event
57
57
58
58
| Metric | Description |
59
59
| ------ | ----------- |
60
-
| deliverySuccessCounts | Number of events successfully delivered to the configured endpoint
61
-
| deliveryFailureCounts | Number of event delivery attempts failed to the configured endpoint
62
-
| deliverySuccessLatencyMs | Latency of events successfully delivered in milliseconds
63
-
| deliveryFailureLatencyMs | Latency of events delivery failures in milliseconds
64
-
| systemDelayForFirstAttemptMs | System delay of events before first delivery attempt in milliseconds
65
-
| deliveryAttemptsCount | Number of event delivery attempts - success and failure
66
-
| expiredCounts | Number of events unable to be delivered
60
+
| DeliverySuccessCounts | Number of events successfully delivered to the configured endpoint
61
+
| DeliveryFailureCounts | Number of events that failed to be delivered to the configured endpoint
62
+
| DeliverySuccessLatencyMs | Latency of events successfully delivered in milliseconds
63
+
| DeliveryFailureLatencyMs | Latency of events delivery failures in milliseconds
64
+
| SystemDelayForFirstAttemptMs | System delay of events before first delivery attempt in milliseconds
65
+
| DeliveryAttemptsCount | Number of event delivery attempts - success and failure
66
+
| ExpiredCounts | Number of events that expired and were not delivered to the configured endpoint
@@ -151,7 +152,7 @@ Instead of a docker volume, you also have the option to mount a host folder.
151
152
```
152
153
153
154
>[!IMPORTANT]
154
-
>Do not change the second part of the bind value. It points to a specific location within the module. For the Event Grid module on linux, it has to be **/app/metadata**.
155
+
>Do not change the second part of the bind value. It points to a specific location within the module. For the Event Grid module on linux, it has to be **/app/metadataDb** and **/app/eventsDb**
155
156
156
157
157
158
## Persist events
@@ -162,7 +163,7 @@ Important things to note about persisting events:
162
163
163
164
* Persisting events is enabled on a per Event Subscription basis and is opt-in once a volume or directory has been mounted.
164
165
* Event persistence is configured on an Event Subscription at creation time and cannot be modified once the Event Subscription is created. To toggle event persistence, you must delete and re-create the Event Subscription.
165
-
* Persisting events is almost always slower than in memory operations, however the speed difference is highly dependent on the characteristics of the drive. The tradeoff between speed and reliability is inherent to all messaging systems but generally only becomes a noticible at large scale.
166
+
* Persisting events is almost always slower than in memory operations, however the speed difference is highly dependent on the characteristics of the drive. The tradeoff between speed and reliability is inherent to all messaging systems but generally only becomes a noticeable at large scale.
166
167
167
168
To enable event persistence on an Event Subscription, set`persistencePolicy` to `true`:
168
169
@@ -180,4 +181,4 @@ To enable event persistence on an Event Subscription, set `persistencePolicy` to
Copy file name to clipboardExpand all lines: articles/event-grid/edge/persist-state-windows.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,13 +207,13 @@ Instead of mounting a volume, you can create a directory on the host system and
207
207
```
208
208
## Persist events
209
209
210
-
To enable event persistence, you must first enablemetadata persistence either via volume mount or host directory mount using the above sections.
210
+
To enable event persistence, you must first enableevents persistence either via volume mount or host directory mount using the above sections.
211
211
212
212
Important things to note about persisting events:
213
213
214
214
* Persisting events is enabled on a per Event Subscription basis and is opt-in once a volume or directory has been mounted.
215
215
* Event persistence is configured on an Event Subscription at creation time and cannot be modified once the Event Subscription is created. To toggle event persistence, you must delete and re-create the Event Subscription.
216
-
* Persisting events is almost always slower than in memory operations, however the speed difference is highly dependent on the characteristics of the drive. The tradeoff between speed and reliability is inherent to all messaging systems but only becomes a noticible at large scale.
216
+
* Persisting events is almost always slower than in memory operations, however the speed difference is highly dependent on the characteristics of the drive. The tradeoff between speed and reliability is inherent to all messaging systems but only becomes a noticeable at large scale.
217
217
218
218
To enable event persistence on an Event Subscription, set`persistencePolicy` to `true`:
Copy file name to clipboardExpand all lines: articles/event-grid/edge/pub-sub-events-webhook-local.md
+11-32Lines changed: 11 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,8 +59,7 @@ A deployment manifest is a JSON document that describes which modules to deploy,
59
59
```json
60
60
{
61
61
"Env": [
62
-
"inbound__clientAuth__clientCert__enabled=false",
63
-
"outbound__webhook__httpsOnly=false"
62
+
"inbound__clientAuth__clientCert__enabled=false"
64
63
],
65
64
"HostConfig": {
66
65
"PortBindings": {
@@ -74,21 +73,17 @@ A deployment manifest is a JSON document that describes which modules to deploy,
74
73
}
75
74
```
76
75
1. Click **Save**
77
-
1. Continue to the next section to add the Azure Functions module before deploying them together.
76
+
1. Continue to the next section to add the Azure Event Grid Subscriber module before deploying them together.
78
77
79
78
>[!IMPORTANT]
80
-
> In this tutorial, you will deploy the Event Grid module with client authentication disabled and allow HTTP subscribers. For production workloads, we recommend that you enable the client authentication and allow only HTTPs subscribers. For more information on how to configure Event Grid module securely, see [Security and authentication](security-authentication.md).
79
+
> In this tutorial, you will deploy the Event Grid module with client authentication disabled. For production workloads, we recommend that you enable the client authentication. For more information on how to configure Event Grid module securely, see [Security and authentication](security-authentication.md).
81
80
>
82
81
> If you are using an Azure VM as an edge device, add an inbound port rule to allow inbound traffic on the port 4438. For instructions on adding the rule, see [How to open ports to a VM](../../virtual-machines/windows/nsg-quickstart-portal.md).
83
82
84
83
85
-
## Deploy Azure Function IoT Edge module
86
-
87
-
This section shows you how to deploy the Azure Functions IoT module, which would act as an Event Grid subscriber to which events can be delivered.
88
-
89
-
>[!IMPORTANT]
90
-
>In this section, you will deploy a sample Azure Function-based subscribing module. It can of course be any custom IoT Module that can listen for HTTP POST requests.
84
+
## Deploy Event Grid Subscriber IoT Edge module
91
85
86
+
This section shows you how to deploy another IoT module which would act as an event handler to which events can be delivered.
92
87
93
88
### Add modules
94
89
@@ -97,23 +92,8 @@ This section shows you how to deploy the Azure Functions IoT module, which would
97
92
1. Provide the name, image, and container create options of the container:
> The **endpointType** property specifies that the subscriber is a **Webhook**. The **endpointUrl** specifies the URL at which the subscriber is listening for events. This URL corresponds to the Azure Function sample you deployed earlier.
177
+
> The **endpointType** property specifies that the subscriber is a **Webhook**. The **endpointUrl** specifies the URL at which the subscriber is listening for events. This URL corresponds to the Azure Subscriber sample you deployed earlier.
198
178
2. Run the following command to create a subscription for the topic. Confirm that you see the HTTP status code is `200 OK`.
199
179
200
180
```sh
@@ -218,7 +198,7 @@ Subscribers can register for events published to a topic. To receive any event,
0 commit comments