Merge pull request #234859 from gourdsay/main

Throttling Event Grid and typo edits

Author: PMEds28

articles/data-manager-for-agri/concepts-ingest-sensor-data.md

@@ -34,13 +34,13 @@ Gateways collect all essential data from the nodes and push it securely to the c
 
 In addition to the above approach, IOT devices (sensors/nodes/gateway) can directly push the data to IOTHub endpoint. In both cases, the data first reaches the IOTHub, post that the next set of processing happens.  
 
->:::image type="content" source="./media/sensor-data-flow-new.png" alt-text="Screenshot showing sensor data flow.":::
+:::image type="content" source="./media/sensor-data-flow-new.png" alt-text="Screenshot showing sensor data flow.":::
 
 ## Sensor topology
 
 The following diagram depicts the topology of a sensor in Azure Data Manager for Agriculture. Each boundary under a party has a set of devices placed within it. A device can be either be a node or a gateway and each device has a set of sensors associated with it. Sensors send the recordings via gateway to the cloud. Sensors are tagged with GPS coordinates helping in creating a geospatial time series for all measured data.
 
->:::image type="content" source="./media/sensor-topology-new.png" alt-text="Screenshot showing sensor topology.":::
+:::image type="content" source="./media/sensor-topology-new.png" alt-text="Screenshot showing sensor topology.":::
 
 ## Next steps
 

articles/data-manager-for-agri/concepts-isv-solutions.md

@@ -23,7 +23,7 @@ The agriculture industry is going through a significant technology transformatio
 
 The solution framework is built on top of Data Manager for Agriculture that provides extensibility capabilities. It enables our Independent Software Vendor (ISV) partners to apply their deep domain knowledge and develop specialized domain specific industry solutions to top of the core platform.  The solution framework provides below capabilities:
 
->:::image type="content" source="./media/solution-framework-isv-1.png" alt-text="Screenshot showing ISV solution framework.":::
+:::image type="content" source="./media/solution-framework-isv-1.png" alt-text="Screenshot showing ISV solution framework.":::
 
 * Enables ISV Partners to easily build industry specific solutions to top of Data Manager for Agriculture.  
 * Helps ISVs generate revenue by monetizing their solution and publishing it on the Azure Marketplace* Provides simplified onboarding experience for ISV Partners and customers.

articles/data-manager-for-agri/concepts-understanding-throttling.md

@@ -0,0 +1,98 @@
+---
+title: API throttling guidance for customers using Azure Data Manager for Agriculture.
+description: Provides information on API throttling limits to plan usage. 
+author: gourdsay
+ms.author: angour
+ms.service: data-manager-for-agri
+ms.topic: conceptual
+ms.date: 04/18/2023
+ms.custom: template-concept
+---
+
+# API throttling guidance for Azure Data Manager for Agriculture.
+
+The API throttling in Azure Data Manager for Agriculture allows more consistent performance within a time span for customers calling our service APIs. Throttling limits, the number of requests to our service in a time span to prevent overuse of resources. Azure Data Manager for Agriculture is designed to handle a high volume of requests, if an overwhelming number of requests occur by few customers, throttling helps maintain optimal performance and reliability for all customers.
+
+Throttling limits vary based on product type and capabilities being used. Currently we have two versions, standard and basic (for your POC needs).
+
+## DPS API limits 
+
+Throttling category |	Units available per Standard version|	Units available per Basic version |
+|:------|:------|:------|
+Per Minute	| 25,000 |	25,000 |
+Per 5 Minutes|	100,000|	100,000 |
+Per Month|	25,000,000|	5,000,000|
+
+### Maximum requests allowed per type for standard version
+API Type|	Per minute|	Per 5 minutes|	Per month|
+|:------|:------|:------|:------|
+PUT	|5,000	|20,000	|5,000,000
+PATCH	|5,000	|20,000	|5,000,000
+POST	|5,000	|20,000	|5,000,000
+DELETE	|5,000	|20,000	|5,000,000
+GET (single object)	|25,000	|100,000	|25,000,000
+LIST with paginated response	|25,000 results	|100,000 results	|25,000,000 results
+
+### Maximum requests allowed per type for basic version
+API Type|	Per minute|	Per 5 minutes|	Per month|
+|:------|:------|:------|:------|
+PUT	|5,000	|20,000	|1,000,000
+PATCH	|5,000	|20,000	|1,000,000
+POST	|5,000	|20,000	|1,000,000
+DELETE	|5,000	|20,000	|1,000,000
+GET (single object)	|25,000	|100,000	|5,000,000
+LIST with paginated response	|25,000 results	|100,000 results	|5,000,000 results
+
+### Throttling cost by API type
+API Type|	Cost per request| 
+|:------|:------:|
+PUT	|5
+PATCH	|5
+POST	|5
+DELETE	|5
+GET (single object)	|1
+GET Sensor Events	|1 + 0.01 per result
+LIST with paginated response	|1 per request + 1 per result
+
+## Jobs create limits per instance of our service
+The maximum queue size for each job type is 10,000.
+
+### Total units available
+Throttling category|	Units available per Standard version|	Units available per Basic version|
+|:------|:------|:------|
+Per 5 Minutes	|1,000	|1,000
+Per Month	|1,000,000	|200,000
+
+
+### Maximum create job requests allowed for standard version
+Job Type|	Per 5 mins|	Per month|
+|:------|:------|:------|
+Cascade delete|	1,000|	500,000
+Satellite|	1,000|	500,000
+Model inference|	200|	100,000
+Farm Operation|	200|	100,000
+Rasterize|	500|	250,000
+Weather|	500|	250,000
+
+
+### Maximum create job requests allowed for basic version
+Job Type|	Per 5 mins|	Per month
+|:------|:------|:------|
+Cascade delete|	1,000|	100,000
+Satellite|	1,000|	100,000
+Model inference|	200|	20,000
+Farm Operation|	200|	20,000
+Rasterize|	500|	50,000
+Weather|	500|	50,000
+
+### Sensor events limits
+100,000 event ingestion per hour by our sensor job.
+
+## Error code
+When you reach the limit, you receive the HTTP status code **429 Too many requests**. The response includes a **Retry-After** value, which specifies the number of seconds your application should wait (or sleep) before sending the next request. If you send a request before the retry value has elapsed, your request isn't processed and a new retry value is returned.
+
+After waiting for specified time, you can also close and reopen your connection to Azure Data Manager for Agriculture. 
+
+## Next steps
+* See the Hierarchy Model and learn how to create and organize your agriculture data  [here](./concepts-hierarchy-model.md).
+* Understand our APIs [here](/rest/api/data-manager-for-agri).

articles/data-manager-for-agri/how-to-set-up-isv-solution.md

@@ -15,7 +15,7 @@ Once you've installed an ISV solution from Azure portal, use this document to un
 
 A high level view of how you can create a new request and get responses from the ISV partners solution:
 
->:::image type="content" source="./media/3p-solutions-new.png" alt-text="Screenshot showing access flow for ISV API.":::
+:::image type="content" source="./media/3p-solutions-new.png" alt-text="Screenshot showing access flow for ISV API.":::
 
 * Step 1: You make an API call for a PUT request with the required parameters (for example Job ID, Farm details)
     * The Data Manager API receives this request and authenticates it.  If the request is invalid, you'll get an error code back.

articles/data-manager-for-agri/how-to-set-up-sensors-customer.md

@@ -29,7 +29,7 @@ To start using the on-boarded sensor partners, you need to give consent to the s
 
 5. Now, look for `Davis Instruments WeatherLink Data Manager for Agriculture Connector` under All Applications tab in `App Registrations` page (illustrated with a generic Partner in the image).
 
-    >:::image type="content" source="./media/sensor-partners.png" alt-text="Screenshot showing the partners message.":::
+   :::image type="content" source="./media/sensor-partners.png" alt-text="Screenshot showing the partners message.":::
 
 6. Copy the Application (client) ID for the specific partner app that you want to provide access to.
 
@@ -44,7 +44,7 @@ Log in to <a href="https://portal.azure.com" target=" blank">Azure portal</a> an
 
 You find the IAM (Identity Access Management) menu option on the left hand side of the option pane as shown in the image:
 
->:::image type="content" source="./media/role-assignment-1.png" alt-text="Screenshot showing role assignment.":::
+:::image type="content" source="./media/role-assignment-1.png" alt-text="Screenshot showing role assignment.":::
 
 Click **Add > Add role assignment**, this action opens up a pane on the right side of the portal, choose the  role from the dropdown:
 
@@ -60,7 +60,7 @@ To complete the role assignment, do the following steps:
 
 4. Click **Save** to assign the role.
 
->:::image type="content" source="./media/sensor-partner-role.png" alt-text="Screenshot showing app selection for authorization.":::
+:::image type="content" source="./media/sensor-partner-role.png" alt-text="Screenshot showing app selection for authorization.":::
 
 This step ensures that the sensor partner app has been granted access (based on the role assigned) to Azure Data Manager for Agriculture  Resource.
 

articles/data-manager-for-agri/how-to-set-up-sensors-partner.md

@@ -17,7 +17,7 @@ The below section of this document talks about the onboarding steps needed to in
 
 Onboarding covers the steps required by both customers & partners to integrate with Data Manager for Agriculture and start receiving/sending sensor telemetry respectively.
 
->:::image type="content" source="./media/sensor-partners-flow.png" alt-text="Screenshot showing sensor partners flow.":::
+:::image type="content" source="./media/sensor-partners-flow.png" alt-text="Screenshot showing sensor partners flow.":::
 
 From the above figure, the blocks highlighted in white are the steps taken by a partner, and the ones highlighted in black are done by customers.