Skip to content

Commit 317c10b

Browse files
committed
image fix
1 parent 08b498f commit 317c10b

File tree

2 files changed

+1
-1
lines changed

2 files changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The application sends data to a [data collection endpoint (DCE)](../essentials/d
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/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":::
18+
:::image type="content" source="media/logs-ingestion-api-overview/overview-log-ingestion-api.png" lightbox="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)