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/iot-operations/connect-to-cloud/howto-create-dataflow-graph.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ ai-usage: ai-assisted
18
18
19
19
A data flow graph is a composable processing pipeline that transforms data as it moves between sources and destinations. A standard [data flow](howto-create-dataflow.md) follows a fixed enrich, filter, map sequence. A data flow graph lets you chain transforms in any order, branch into parallel paths, and aggregate data over time windows.
20
20
21
-
<!--This article walks through creating a data flow graph step by step. For an overview of data flow graphs and the available transforms, see [Data flow graphs overview](concept-dataflow-graphs.md).-->
21
+
This article walks through creating a data flow graph step by step. For an overview of data flow graphs and the available transforms, see [Data flow graphs overview](concept-dataflow-graphs.md).
22
22
23
23
> [!IMPORTANT]
24
24
> Data flow graphs currently support only MQTT, Kafka, and OpenTelemetry endpoints. Other endpoint types like Data Lake, Microsoft Fabric OneLake, Azure Data Explorer, and Local Storage aren't supported. For more information, see [Known issues](../troubleshoot/known-issues.md#data-flow-graphs-only-support-specific-endpoint-types).
@@ -51,7 +51,7 @@ A data flow graph contains three types of elements: **sources** that bring data
51
51
52
52
:::image type="content" source="media/howto-create-dataflow-graph/source-configuration.png" alt-text="Screenshot of the operations experience source configuration panel showing endpoint dropdown and topic input." lightbox="media/howto-create-dataflow-graph/source-configuration.png":::
53
53
54
-
<!--1. **Add transforms**: Select one or more transforms to process the data. Available transforms include map, filter, branch, concat, and window. For details on each transform type, see [Data flow graphs overview](concept-dataflow-graphs.md#available-transforms).-->
54
+
1.**Add transforms**: Select one or more transforms to process the data. Available transforms include map, filter, branch, concat, and window. For details on each transform type, see [Data flow graphs overview](concept-dataflow-graphs.md#available-transforms).
55
55
56
56
:::image type="content" source="media/howto-create-dataflow-graph/transform-selection.png" alt-text="Screenshot of the operations experience transform selection menu showing available transform types." lightbox="media/howto-create-dataflow-graph/transform-selection.png":::
57
57
@@ -278,10 +278,10 @@ The available built-in transforms are:
278
278
279
279
For detailed configuration of each transform type, see:
280
280
281
-
<!-- - [Transform data with map](howto-dataflow-graphs-map.md)
281
+
- [Transform data with map](howto-dataflow-graphs-map.md)
282
282
- [Filter and route data](howto-dataflow-graphs-filter-route.md)
283
283
- [Aggregate data over time](howto-dataflow-graphs-window.md)
284
-
- [Enrich with external data](howto-dataflow-graphs-enrich.md) -->
284
+
- [Enrich with external data](howto-dataflow-graphs-enrich.md)
285
285
286
286
# [Operations experience](#tab/portal)
287
287
@@ -404,7 +404,7 @@ Select the destination element and configure:
404
404
405
405
---
406
406
407
-
<!-- For dynamic topic routing based on message content, see [Route messages to different topics](howto-dataflow-graphs-topic-routing.md). -->
407
+
For dynamic topic routing based on message content, see [Route messages to different topics](howto-dataflow-graphs-topic-routing.md).
0 commit comments