Skip to content

Commit f4b1c4e

Browse files
Update 2017-10-18-two-types-of-correlation.markdown
1 parent 44703b7 commit f4b1c4e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/posts/2017-10-18-two-types-of-correlation.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ When you have an Application Map is in a form of a star, you may notice that som
2222
```
2323
dependencies
2424
| join requests on $left.id == $right.operation_ParentId
25-
| summarize sum(itemCount) by from = cloud_RoleName1, to = cloud_RoleName
25+
| summarize sum(itemCount) by from = cloud_RoleName, to = cloud_RoleName1
2626
```
2727

2828
This query joins outgoing from component `A` dependency call to the request incoming to the component `B`. Now you can see a map where every node is a separate `cloud_RoleName`. Note, that some of dependency calls are made to external components. To draw those you'd still need to use a target field from before. With the slight modification - you need to group it by `cloud_roleName`:
@@ -244,4 +244,4 @@ This picture shows how application map looks like:
244244

245245
## Future directions
246246

247-
There are many improvements coming in the Application Insights distributed applications monitoring story. Specifically for Application Map we are working on optimizing join queries and speed up the map rendering. Application Map is more reliable with metric pre-aggregations. There will be advanced filtering and grouping capabilities to slice and dice the map.
247+
There are many improvements coming in the Application Insights distributed applications monitoring story. Specifically for Application Map we are working on optimizing join queries and speed up the map rendering. Application Map is more reliable with metric pre-aggregations. There will be advanced filtering and grouping capabilities to slice and dice the map.

0 commit comments

Comments
 (0)