From 426fe0840bb25dd14b6d75494c4dc9bc1ccfe232 Mon Sep 17 00:00:00 2001 From: Kai Walter Date: Thu, 25 Jun 2020 16:30:21 +0000 Subject: [PATCH 1/2] issue #1698 resolution --- howto/diagnose-with-tracing/azure-monitor.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/howto/diagnose-with-tracing/azure-monitor.md b/howto/diagnose-with-tracing/azure-monitor.md index 1d34c1af3..f279b83ad 100644 --- a/howto/diagnose-with-tracing/azure-monitor.md +++ b/howto/diagnose-with-tracing/azure-monitor.md @@ -162,6 +162,8 @@ Deploy and run some applications. After a few minutes, you should see tracing lo ![Application map](../../images/azure-monitor.png) +> **NOTE**: For **Application Map** to display the correct topology - and with that rendering `requests` and `dependencies` item types correctly - all apps or services which invoke methods over Dapr need to be operated with a Dapr sidecar. Dapr client invocations from an outside app or service (not operated with a sidecar), are not captured. + ## Tracing configuration The `tracing` section under the `Configuration` spec contains the following properties: From bb3d0b6b2963c116b0d1371a5e27d2dc2702dddb Mon Sep 17 00:00:00 2001 From: Kai Walter Date: Tue, 7 Jul 2020 14:26:01 +0000 Subject: [PATCH 2/2] changing note as requested --- howto/diagnose-with-tracing/azure-monitor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/howto/diagnose-with-tracing/azure-monitor.md b/howto/diagnose-with-tracing/azure-monitor.md index f279b83ad..ed4dda01f 100644 --- a/howto/diagnose-with-tracing/azure-monitor.md +++ b/howto/diagnose-with-tracing/azure-monitor.md @@ -162,7 +162,7 @@ Deploy and run some applications. After a few minutes, you should see tracing lo ![Application map](../../images/azure-monitor.png) -> **NOTE**: For **Application Map** to display the correct topology - and with that rendering `requests` and `dependencies` item types correctly - all apps or services which invoke methods over Dapr need to be operated with a Dapr sidecar. Dapr client invocations from an outside app or service (not operated with a sidecar), are not captured. +> **NOTE**: Only operations going through Dapr API exposed by Dapr sidecar (e.g. service invocation or event publishing) will be displayed in Application Map topology. Direct service invocations (not going through the Dapr API) will not be shown. ## Tracing configuration