Skip to content

Commit c31ae23

Browse files
Merge pull request #289479 from dominicbetts/release-aio-m3-qs-fabric
AIO [M3]: Minor quickstart updates
2 parents 38c181c + e5716f4 commit c31ae23

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed
-1.6 KB
Loading

articles/iot-operations/get-started-end-to-end-sample/quickstart-get-insights.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: baanders
66
ms.topic: quickstart
77
ms.custom:
88
- ignite-2023
9-
ms.date: 10/23/2024
9+
ms.date: 10/30/2024
1010

1111
#CustomerIntent: As an OT user, I want to create a visual report for my processed OPC UA data that I can use to analyze and derive insights from it.
1212
---
@@ -87,6 +87,7 @@ In this section, you create a KQL database in your Microsoft Fabric workspace to
8787
| Spike | boolean |
8888
| Temperature | decimal |
8989
| FillWeight | decimal |
90+
| EnergyUse | decimal |
9091
| Timestamp | datetime |
9192

9293
1. After the *OPCUA* table has been created, select it and use the **Explore your data** button to open a query window for the table.
@@ -96,7 +97,7 @@ In this section, you create a KQL database in your Microsoft Fabric workspace to
9697
1. Run the following KQL query to create a data mapping for your table. The data mapping will be called *opcua_mapping*.
9798

9899
```kql
99-
.create table ['OPCUA'] ingestion json mapping 'opcua_mapping' '[{"column":"AssetId", "Properties":{"Path":"$[\'AssetId\']"}},{"column":"Spike", "Properties":{"Path":"$.Spike"}},{"column":"Temperature", "Properties":{"Path":"$.TemperatureF"}},{"column":"FillWeight", "Properties":{"Path":"$.FillWeight.Value"}},{"column":"Timestamp", "Properties":{"Path":"$[\'EventProcessedUtcTime\']"}}]'
100+
.create table ['OPCUA'] ingestion json mapping 'opcua_mapping' '[{"column":"AssetId", "Properties":{"Path":"$[\'AssetId\']"}},{"column":"Spike", "Properties":{"Path":"$.Spike"}},{"column":"Temperature", "Properties":{"Path":"$.TemperatureF"}},{"column":"FillWeight", "Properties":{"Path":"$.FillWeight.Value"}},{"column":"EnergyUse", "Properties":{"Path":"$.EnergyUse.Value"}},{"column":"Timestamp", "Properties":{"Path":"$[\'EventProcessedUtcTime\']"}}]'
100101
```
101102
102103
### Add data table as a destination
@@ -179,7 +180,7 @@ Next, add a tile to your dashboard to show a line chart of temperature and its s
179180
OPCUA
180181
| where Timestamp between (_startTime .. _endTime)
181182
| project Timestamp, Temperature, Spike
182-
| extend SpikeMarker = iff(Spike == true, Temperature, double(null))
183+
| extend SpikeMarker = iff(Spike == true, Temperature, decimal(null))
183184
```
184185
185186
**Run** the query to verify that data can be found.
@@ -193,7 +194,7 @@ Next, add a tile to your dashboard to show a line chart of temperature and its s
193194
- **Data**:
194195
- **Y columns**: *Temperature (decimal)*, *Spike (boolean)* (already inferred by default)
195196
- **X columns**: *Timestamp (datetime)* (already inferred by default)
196-
- **Series columns**: *SpikeMarker*
197+
- **Series columns**: Leave the default inferred value.
197198
- **Y Axis**:
198199
- **Label**: *Units*
199200
- **X Axis**:
@@ -229,7 +230,7 @@ Next, create a tile to display a real-time spike indicator for temperature.
229230
- **Value column**: *Temperature (decimal)* (already inferred by default)
230231
- **Conditional formatting**: Select **+ Add rule** and select the pencil icon to edit the rule.
231232
- **Conditions**: Use the entry form to enter the condition *Spike == true*.
232-
- **Color**: Select *Red* and choose an alert *Icon*.
233+
- **Color**: Select *Red* and choose the warning icon.
233234
234235
:::image type="content" source="media/quickstart-get-insights/conditional-formatting.png" alt-text="Screenshot of the conditional formatting options.":::
235236

0 commit comments

Comments
 (0)