Affinity Groups

Affinity Groups Overview

Beginning in version 15.03, Device42 has added Affinity Group Analysis. This new feature assists customers and partners with application grouping activities based on observed communication patterns.

After discovery has been run within the environment (recommended 30 days minimum), detailed application dependency information has been collected. Information collected includes service names and communication details. Affinities are then calculated based on client communication to a particular service listening on a TCP or UDP port and server process. Users define services critical to their use case then affinity groups are processed. The result is a visualized grouping of communication patterns.

Using Affinity Groups – How-To

1) From the Device42 menu, navigate to Reports > Advanced Reporting
In the Pre-Defined Reports folder, you will see Affinity Group Analysis. Execute the “Affinity Group Analysis” report and download the results (in .CSV format!):

Run Affinity Group Analysis Report from Advanced Reporting

2) Navigate to the external Affinity Group processing application at https://movegroups.device42.io. Create a login if you don’t already have one (sign up). Optionally, provide a label for your report, and upload the .CSV of the report file you previously exported:

Upload Affinity Group Analysis Report at movegroups.device42.io

3) Categorize Services and configure Affinty Groups.

a. Click the ‘Service Categorization’ button to view a deduplicated listing of all services discovered within your environment. Simply label each of your discovered services as either Infrastructure or Application via import, export, or UI:

Categorize discovered services

b. Select the appropriate filters for your use case. You may choose from:

  • Ignore local listeners – local listeners such as 127.0.0.1 or the locally registered IP address are frequently ignored when performing lift and shift migrations. However, if multiple local applications are being divided to operate on separate servers in the target operating model, one should consider including these connections in their analysis.
  • Ignore IPv6 – IPv6 is commonly loaded into the TCP/IP bindings. However, many users are not using IPv6 today. If you are not using IPv6, ignore IPv6 to reduce further application dependency analysis.
  • Ignore service without connections – Device42 increments the service port connection counts with each discovery. If you are comfortable with the sample period of your discovery, service ports showing zero connections should be ignored.
  • Ignore undiscovered clients – In engagements where the scope of hosts is clearly defined, you may only want to include discovered hosts in your analysis.
  • Show mixed groups connections – Toggle this setting to show connections between infrastructure, application and undefined groups

    c. Choose which type of relationships you would like to export:

  • Impact – impact of an outage, performance issues, or security issue on a data center object
  • Dependent – visualize the objects or services this data center object is dependent upon
  • Both – impact and dependent

4) Click Generate Affinity Groups – This will generate a .zip file to be imported back into Device42.

a. From the Device42 menu, navigate to Apps > Affinity Groups

b. Click “Upload Affinity Groups”, select your zip file and click Upload.

Once the import is complete, Affinity Groups can be visualized within the Device42 User Interface:

Visualize Affinity Group Results