From 426fe0840bb25dd14b6d75494c4dc9bc1ccfe232 Mon Sep 17 00:00:00 2001 From: Kai Walter Date: Thu, 25 Jun 2020 16:30:21 +0000 Subject: [PATCH] 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: