Skip to content

Commit 6d6d0fa

Browse files
author
Kai Nawroth
authored
Update export-telemetry.md
1 parent cefc56f commit 6d6d0fa

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/azure-monitor/app/export-telemetry.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -272,6 +272,8 @@ To migrate to diagnostic settings export:
272272
> If you want to store diagnostic logs in a Log Analytics workspace, there are two things to consider to avoid seeing duplicate data in Application Insights:
273273
> * The destination can't be the same Log Analytics workspace that your Application Insights resource is based on.
274274
> * The Application Insights user can't have access to both workspaces. This can be done by setting the Log Analytics [Access control mode](/azure/azure-monitor/logs/log-analytics-workspace-overview#permissions) to **Requires workspace permissions** and ensuring through [Azure role-based access control (Azure RBAC)](./resources-roles-access-control.md) that the user only has access to the Log Analytics workspace the Application Insights resource is based on.
275+
>
276+
> These steps are necessary because Applications Insights accumulates telemetry across different Log Analyticics workspaces and uses the same table names for diagnostic logs, leading to duplicate data in Application Insights.
275277
276278
<!--Link references-->
277279

0 commit comments

Comments
 (0)