When you edit existing flow maps or create new customized flow maps, you can group similar databases or remote services into a single icon.
Some reasons to group similar backends into a single icon are to improve readability or focus on nodes of specific business interest. For example if individual databases or remote service instances are not important to the audience using this specific flow map, you can group them into one icon.
Configure Backend Icons on Flow Maps
In the Edit Flow Map window you can configure how backends are displayed in flow maps.
In a flow map, click Flow Map Name -> Edit Flow Map.
- Group databases and remote services of the same type. By default AppDynamics groups any two or more backends of the same type. Sometimes you want to see each database and remote service in the flow map. If so, uncheck this option.
- If there are specific database or remote services that you do not want to see or group in the flow map, uncheck the Visible or Groupable check box.
Rules for Grouping Backends on Flow Maps
Not every backend can be grouped into the same tier. These rules govern how databases and remote services can be grouped on flow maps.
- A group consists of a minimum of two backends.
- A backend that calls other backends or calls into any other tiers cannot be part of a backend group.
A set of backends can be grouped under these conditions:
1. The backends are all of the same type.
2. The backends are called by the same tiers.
For example, consider the case shown in the top half of the following diagram where:
- Tier 1 calls Backend 1, Backend 2, Backend 3, and
- Tier 2 calls Backend 1, Backend 3, Backend 4, and
- Backend 4 calls Backend 5
The bottom half of the diagram shows that Backend 1 and Backend 3 can be grouped because they are called by Tier 1 and Tier 2. However, Backend 2 and Backend 5 can not be grouped because they are individual backends of a type within their tiers. Backend 4 cannot be grouped because it calls Backend 5.