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/data-manager-for-agri/how-to-use-events.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,17 +52,18 @@ To learn more about how to apply filters, see <a href = "https://docs.microsoft.
52
52
## Subscribing to events
53
53
You can subscribe to Data Manager for Agriculture events by using Azure portal or Azure Resource Manager client. Each of these provide the user with a set of functionalities. Refer to following resources to know more about each method.
54
54
55
-
1. <ahref = "https://docs.microsoft.com/azure/event-grid/subscribe-through-portal#:~:text=Create%20event%20subscriptions%201%20Select%20All%20services.%202,event%20types%20option%20checked.%20...%20More%20items..."target = "_blank"> Subscribe to events using portal </a>
56
-
2. <ahref = "https://docs.microsoft.com/azure/event-grid/sdk-overview"target = "_blank"> Subscribe to events using the ARM template client </a>
55
+
<ahref = "https://docs.microsoft.com/azure/event-grid/subscribe-through-portal#:~:text=Create%20event%20subscriptions%201%20Select%20All%20services.%202,event%20types%20option%20checked.%20...%20More%20items..."target = "_blank"> Subscribe to events using portal </a>
56
+
57
+
<ahref = "https://docs.microsoft.com/azure/event-grid/sdk-overview"target = "_blank"> Subscribe to events using the ARM template client </a>
57
58
58
59
## Practices for consuming events
59
60
60
61
Applications that handle Data Manager for Agriculture events should follow a few recommended practices:
61
62
62
-
1. Check that the eventType is one you're prepared to process, and don't assume that all events you receive are the types you expect.
63
-
2. As messages can arrive out of order, use the modifiedTime and etag fields to understand the order of events for any particular object.
64
-
3. Data Manager for Agriculture events guarantees at-least-once delivery to subscribers, which ensures that all messages are outputted. However due to retries or availability of subscriptions, duplicate messages may occasionally occur. To learn more about message delivery and retry, see <ahref = "https://docs.microsoft.com/azure/event-grid/delivery-and-retry"target = "_blank">Event Grid message delivery and retry </a>
65
-
4. Ignore fields you don't understand. This practice will help keep you resilient to new features that might be added in the future.
63
+
* Check that the eventType is one you're prepared to process, and don't assume that all events you receive are the types you expect.
64
+
* As messages can arrive out of order, use the modifiedTime and etag fields to understand the order of events for any particular object.
65
+
* Data Manager for Agriculture events guarantees at-least-once delivery to subscribers, which ensures that all messages are outputted. However due to retries or availability of subscriptions, duplicate messages may occasionally occur. To learn more about message delivery and retry, see <ahref = "https://docs.microsoft.com/azure/event-grid/delivery-and-retry"target = "_blank">Event Grid message delivery and retry </a>
66
+
* Ignore fields you don't understand. This practice will help keep you resilient to new features that might be added in the future.
66
67
67
68
68
69
### Available event types
@@ -106,7 +107,7 @@ Applications that handle Data Manager for Agriculture events should follow a few
106
107
|Microsoft.AgFoodPlatform.SensorPlacementModelJobStatusChangedV2|Published when Sensor Placement Model Job status is changed
107
108
108
109
109
-
### Event Properties
110
+
### Event properties
110
111
111
112
Each Azure Data Manager for Agriculture event has two parts, the first part is common across events and the second, data object contains properties specific to each event.
112
113
@@ -396,7 +397,7 @@ Property| Type| Description
396
397
|:-----| :----| :----|
397
398
managementZoneId| string | Management Zone ID associated with the zone.
398
399
partyId| string | User-defined ID of associated field.
399
-
| ID | string| Id of the party it belongs tos
400
+
| ID | string| Id of the party it belongs to
400
401
status| string| Contains the user defined status of the resource.
401
402
actionType| string| Indicates the change that triggered publishing of the event. Applicable values are created, updated, deleted.
402
403
modifiedDateTime| date-time|Date-time when resource was last modified, sample format: yyyy-MM-ddTHH:mm:ssZ.
@@ -478,7 +479,7 @@ name| string| User-defined name of the nutrient analysis.
478
479
479
480
480
481
## Sample events
481
-
For Sample events, refer to [this](./sample_events.md) page
482
+
For Sample events, refer to [this](./sample-events.md) page
482
483
483
484
## Next steps
484
485
* For an introduction to Azure Event Grid, see [What is Event Grid?](../event-grid/overview.md)
0 commit comments