Skip to content

Commit 6917274

Browse files
committed
image-fix
1 parent 8152042 commit 6917274

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/azure-monitor/logs/logs-ingestion-api-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ The Logs Ingestion API in Azure Monitor lets you send data to a Log Analytics wo
1111

1212
## Basic operation
1313
Data can be sent to the Logs Ingestion API from any application that can make a REST API call. This may be a custom application that you create, or it may be an application or agent that understands how to send data to the API.
14-
The application sends data to a [data collection endpoint (DCE)](../essentials/logs-ingestion-api-overview/logs-ingestion-api-overview.md), which is a unique connection point for your Azure subscription. It specifies a [data collection rule (DCR)](../essentials/logs-ingestion-api-overview/logs-ingestion-api-overview.md) that includes the target table and workspace and the credentials of an app registration with access to the specified DCR.
14+
The application sends data to a [data collection endpoint (DCE)](../essentials/data-collection-endpoint-overview.md), which is a unique connection point for your Azure subscription. It specifies a [data collection rule (DCR)](../essentials/data-collection-rule-overview.md) that includes the target table and workspace and the credentials of an app registration with access to the specified DCR.
1515

1616
The data sent by your application to the API must be formatted in JSON and match the structure expected by the DCR. It doesn't necessarily need to match the structure of the target table because the DCR can include a [transformation](../essentials//data-collection-transformations.md) to convert the data to match the table's structure. You can modify the target table and workspace by modifying the DCR without any change to the API call or source data.
1717

18-
:::image type="content" source="../essentials/media/data-collection-rule-overview/overview-log-ingestion-api.png" lightbox="../essentials/media/data-collection-rule-overview/overview-log-ingestion-api.png" alt-text="Diagram that shows an overview of logs ingestion API." border="false":::
18+
:::image type="content" source="../essentials/media/logs-ingestion-api-overview/overview-log-ingestion-api.png" lightbox="../essentials/media/logs-ingestion-api-overview/overview-log-ingestion-api.png" alt-text="Diagram that shows an overview of logs ingestion API." border="false":::
1919

2020
## Configuration
2121
The following table describes each component in Azure that you must configure before you can use the Logs Ingestion API.

0 commit comments

Comments
 (0)