Skip to content

Commit 2a7c9e1

Browse files
authored
Merge pull request #109624 from uhabiba04/master
minor format fix
2 parents 4ed1a22 + dcf516f commit 2a7c9e1

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

articles/industry/agriculture/troubleshoot-azure-farmbeats.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,9 @@ To download the **deployer.log** file, do the following:
3333
**Corrective action**:
3434

3535
1. Go to your FarmBeats Datahub resource group. 
36+
3637
2. Select the **Event Hub** (DatafeedEventHubNamespace), and then check for the number of incoming messages.
38+
3739
3. Do either of the following: 
3840
- If there are *no incoming messages*, contact your device partner.
3941
- If there are *incoming messages*, contact [email protected]. Attach your Datahub and Accelerator logs and captured telemetry.
@@ -47,6 +49,7 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
4749
**Corrective action**:
4850

4951
1. Ensure you have done the partner registration correctly - you can check this by going to your datahub swagger, navigate to /Partner API, Do a Get and check if the partner is registered. If not, follow the [steps here](get-sensor-data-from-sensor-partner.md#enable-device-integration-with-farmbeats) to add partner.
52+
5053
2. Ensure that you have used the correct Telemetry message format:
5154

5255
```json
@@ -78,9 +81,12 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
7881

7982
1. In Datahub Swagger, go to the Partner API.
8083
2. Select **Get** > **Try it out** > **Execute**.
81-
3. Note the partner ID of the sensor partner you're interested in.
82-
4. Go back to the Partner API, and select **Get/\<ID>**.
83-
5. Specify the partner ID from step 3, and then select **Execute**.
84+
85+
> [!NOTE]
86+
> The partner ID of the sensor partner you're interested in.
87+
88+
3. Go back to the Partner API, and select **Get/\<ID>**.
89+
4. Specify the partner ID from step 3, and then select **Execute**.
8490

8591
The API response should have the Event Hubs connection string.
8692

0 commit comments

Comments
 (0)