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/industry/agriculture/troubleshoot-azure-farmbeats.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,9 @@ To download the **deployer.log** file, do the following:
33
33
**Corrective action**:
34
34
35
35
1. Go to your FarmBeats Datahub resource group.
36
+
36
37
2. Select the **Event Hub** (DatafeedEventHubNamespace), and then check for the number of incoming messages.
38
+
37
39
3. Do either of the following:
38
40
- If there are *no incoming messages*, contact your device partner.
39
41
- 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
47
49
**Corrective action**:
48
50
49
51
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
+
50
53
2. Ensure that you have used the correct Telemetry message format:
51
54
52
55
```json
@@ -78,9 +81,12 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
78
81
79
82
1. In Datahub Swagger, go to the Partner API.
80
83
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**.
84
90
85
91
The API response should have the Event Hubs connection string.
0 commit comments