Skip to content

Commit 0aed08a

Browse files
committed
overview diagram
1 parent 9f3be8c commit 0aed08a

File tree

2 files changed

+8
-1
lines changed

2 files changed

+8
-1
lines changed

articles/azure-monitor/essentials/edge-pipeline-configure.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ author: bwren
99

1010
# Configuration of Azure Monitor edge pipeline
1111

12+
- Pipeline has small p
13+
14+
1215
[Azure Monitor pipeline](./pipeline-overview.md) is a data ingestion pipeline providing consistent and centralized data collection for Azure Monitor. The [edge pipeline](./pipeline-overview.md#edge-pipeline) enables at-scale collection, and routing of telemetry data before it's sent to the cloud. It can cache data locally and sync with the cloud when connectivity is restored and route telemetry to Azure Monitor in cases where the network is segmented and data cannot be sent directly to the cloud. This article describes how to enable and configure the edge pipeline in your environment.
1316

1417
## Overview
@@ -89,14 +92,18 @@ The following tables and diagrams describe the detailed steps and components in
8992
:::image type="content" source="media/edge-pipeline/cloud-pipeline-data-flow.png" lightbox="media/edge-pipeline/cloud-pipeline-data-flow.png" alt-text="Detailed diagram of the steps and components for data collection using Azure Monitor cloud pipeline." border="false":::
9093

9194
## Segmented network
95+
96+
97+
9298
[Network segmentation](/azure/architecture/networking/guide/network-level-segmentation) is a model where you use software defined perimeters to create a different security posture for different parts of your network. In this model, you may have a network segment that can't connect to the internet or to other network segments. The edge pipeline can be used to collect data from these network segments and send it to the cloud pipeline.
9399

94100
:::image type="content" source="media/edge-pipeline/layered-network.png" lightbox="media/edge-pipeline/layered-network.png" alt-text="Diagram of a layered network for Azure Monitor edge pipeline." border="false":::
95101

96102
To use Azure Monitor pipeline in a layered network configuration, you must add the following URLs to the allowlist for the Arc-enabled Kubernetes cluster. See [Configure Azure IoT Layered Network Management Preview on level 4 cluster](/azure/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network?tabs=k3s#configure-layered-network-management-preview-service).
97103

98104
- `*.ingest.monitor.azure.com`
99-
- Url of DCE
105+
- `login.windows.net`
106+
- These are both external type
100107

101108

102109
## Create table in Log Analytics workspace
4.23 KB
Loading

0 commit comments

Comments
 (0)