Configuration and Discovery

Download this manual as a PDF file

The following sections describe how to configure and discover Cisco AppDynamics applications for monitoring by SL1 using the Cisco: AppDynamics PowerPack:

Prerequisites for Monitoring Cisco AppDynamics

Before you can monitor Cisco AppDynamics applications using the Cisco: AppDynamics PowerPack, you must first create a user account and an API Client that is assigned the "Applications and Dashboard Viewer" and "DB Monitoring User" role in the AppDynamics account portal. This user account must also have sufficient permissions to obtain metrics information from the AppDynamics REST API.

For more information about creating the AppDynamics user account, see https://docs.appdynamics.com/display/PRO44/Roles+and+Permissions.

Creating a SOAP/XML Credential for Cisco AppDynamics

To use the Dynamic Applications in the Cisco: AppDynamics PowerPack, you must first define a SOAP/XML credential in SL1. This credential allows SL1 to communicate with the AppDynamics applications.

The Cisco: AppDynamics PowerPack includes a sample credential you can use as a template for creating SOAP/XML credentials for AppDynamics.

To configure a SOAP/XML credential for AppDynamics:

  1. Go to the Credentials page (Manage > Credentials).
  2. Locate the "AppDynamics Example" sample credential, click its Actions icon () and select Duplicate. A copy of the credential appears.
  3. Click the Actions icon () for the "AppDynamics Example copy" credential copy and select Edit. The Edit Credential modal page appears.

  1. Enter values in the following fields:
  • Name. Type a new name for the credential.
  • All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the Select the organizations the credential belongs to drop-down field to align the credential with those specific organizations.
  • URL. Type the URL for the AppDynamics account controller.
  • HTTP Auth User. Type the username of an AppDynamics user account that is assigned the "Applications and Dashboard Viewer" role in the AppDynamics portal.
  • HTTP Auth Password. Type the AppDynamics user account password.
  • Embed Value [%1]. Type your AppDynamics account name.
  1. Click Save & Close.
  2. In the confirmation message, click OK.

Creating a SOAP/XML Credential for Cisco AppDynamics in the SL1 Classic User Interface

To use the Dynamic Applications in the Cisco: AppDynamics PowerPack, you must first define a SOAP/XML credential in SL1. This credential allows SL1 to communicate with the AppDynamics applications.

The Cisco: AppDynamics PowerPack includes a sample credential you can use as a template for creating SOAP/XML credentials for AppDynamics.

To configure a SOAP/XML credential for AppDynamics:

  1. Go to the Credential Management page (System > Manage > Credentials).

  1. Locate the AppDynamics Example credential and then click its wrench icon (). The Edit SOAP/XML Credential modal page appears.

  1. Enter values in the following fields:

Basic Settings

  • Profile Name. Type a new name for the credential.
  • URL. Type the URL for the AppDynamics account controller.
  • HTTP Auth User. Type the username of an AppDynamics user account that is assigned the "Applications and Dashboard Viewer" role in the AppDynamics portal.
  • HTTP Auth Password. Type the AppDynamics user account password.

Proxy Settings

  • Hostname/IP. If you are connecting to AppDynamics via a proxy server, type the server's hostname or IP address. Otherwise, leave this field blank.

  • Port. If you are connecting to AppDynamics via a proxy server, type the port number you opened when setting up the proxy server. Otherwise, leave this field blank.
  • User. If you are connecting to AppDynamics via a proxy server, type the server's administrator username. Otherwise, leave this field blank.
  • Password. If you are connecting to AppDynamics via a proxy server, type the server's administrator password. Otherwise, leave this field blank.

SOAP Options

  • Embed Value [%1]. Type your AppDynamics account name.

  1. Click Save As.
  2. In the confirmation message, click OK.

You must rename the sample AppDynamics Example credential and click Save As to save it. If you do not rename the sample credential, then your credential will be overwritten the next time you upgrade the Cisco: AppDynamics PowerPack.

 

Creating a SOAP/XML Credential with OAuth2 Authentication for Cisco AppDynamics

To use the Dynamic Applications in the Cisco: AppDynamics PowerPack, you must first define a SOAP/XML credential in SL1. This credential allows SL1 to communicate with the AppDynamics applications.

The Cisco: AppDynamics PowerPack includes a sample credential you can use as a template for creating SOAP/XML credentials with OAuth2 authentication for AppDynamics.

To configure a SOAP/XML credential for AppDynamics:

  1. Go to the Credential Management page (Manage>Credentials).
  2. Locate the AppDynamics Example - OAuth sample credential, click its Actions icon () and select Duplicate. A copy of the credential appears.
  3. Click the Actions icon () for the "AppDynamics Example - OAuth copy" credential copy and select Edit. The Edit Credential modal page appears.

  1. Enter values in the following fields:
  • Name. Type a new name for the credential.
  • All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the Select the organizations the credential belongs to drop-down field to align the credential with those specific organizations.
  • URL. Type the URL for the AppDynamics account controller.
  • HTTP Auth User. This field is to remain blank.
  • HTTP Auth Password. This field is to remain blank.
  • Embedded Password [%P]. Type your Client Secret.
  • Embed Value [%1]. Type your AppDynamics account name.
  • Embed Value [%2]. Type your Client Name.
  1. Click Save & Close.
  2. In the confirmation message, click OK.

Creating a SOAP/XML Credential with OAuth2 Authentication for Cisco AppDynamics in the SL1 Classic User Interface

To use the Dynamic Applications in the Cisco: AppDynamics PowerPack, you must first define a SOAP/XML credential in SL1. This credential allows SL1 to communicate with the AppDynamics applications.

The Cisco: AppDynamics PowerPack includes a sample credential you can use as a template for creating SOAP/XML credentials with OAuth2 authentication for AppDynamics.

To configure a SOAP/XML credential for AppDynamics:

  1. Go to the Credential Management page (System > Manage > Credentials).
  2. Locate the AppDynamics Example - OAuth credential and then click its wrench icon (). The Edit SOAP/XML Credential modal page appears.
  3. Enter values in the following fields:

Basic Settings

  • Profile Name. Type a new name for the credential.
  • URL. Type the URL for the AppDynamics account controller.
  • HTTP Auth User. This field is to remain blank.
  • HTTP Auth Password. This field is to remain blank.

Proxy Settings

  • Hostname/IP. If you are connecting to AppDynamics via a proxy server, type the server's hostname or IP address. Otherwise, leave this field blank.

  • Port. If you are connecting to AppDynamics via a proxy server, type the port number you opened when setting up the proxy server. Otherwise, leave this field blank.
  • User. If you are connecting to AppDynamics via a proxy server, type the server's administrator username. Otherwise, leave this field blank.
  • Password. If you are connecting to AppDynamics via a proxy server, type the server's administrator password. Otherwise, leave this field blank.

SOAP Options

  • Embedded Password [%P]. Type your Client Secret.
  • Embed Value [%1]. Type your AppDynamics account name.
  • Embed Value [%2]. Type your Client Name.

  1. Click Save As.
  2. In the confirmation message, click OK.

You must rename the sample AppDynamics Example credential and click Save As to save it. If you do not rename the sample credential, then your credential will be overwritten the next time you upgrade the Cisco: AppDynamics PowerPack.

Creating a SOAP/XML Credential for an SSL Certificate

To use the Dynamic Applications in the "Cisco: AppDynamics" PowerPack, you must first define a SOAP/XML credential in SL1. This credential allows SL1 to communicate with the AppDynamics applications.

The "Cisco: AppDynamics" PowerPack includes a sample credentials you can use as a template.

To configure a SOAP/XML credential:

  1. Go to the Credential Management page (Manage > Credentials).
  2. Locate the AppDynamics Example - SSL sample credential, click its Actions icon (), and select Duplicate. A copy of the credential appears.
  3. Click the Actions icon () for the "AppDynamics Example - SSL copy" credential copy and select Edit. The Edit Credential modal appears.

    4. SSL credential edit modal.

  4. Enter values in the following fields:
  • Name.Type a new name for the credential.
  • All Organizations. Toggle on (blue) to align the credential to all organizations, or toggle off (gray) and then select one or more specific organizations from the Select the organizations the credential belongs to drop-down field to align the credential with those specific organizations.
  • URL. Type the URL for the AppDynamics account controller.
  • HTTP Auth User. Type the username of an AppDynamics user account that is assigned the "Applications and Dashboard Viewer" role in the AppDynamics portal.
  • HTTP Auth Password. Type the AppDynamics user account password.
  • Embed Value [%1]. Type your AppDynamics account name.
  • CURL options: Edit the following field in this section
    • CAPATH. Type the certificate path for your SSL certificate.
    • SSLVERIFYPEER=1. Enables the SSL verification.
  1. Click Save & Close.
  2. In the confirmation message, click OK.

Creating a SOAP/XML Credential for an SSL Certificate in the SL1 Classic User Interface

To configure a SOAP/XML credential for AppDynamics:

  1. Go to the Credential Management page (System > Manage > Credentials).
  2. Locate the AppDynamics Example – SSL credential and then click its wrench icon ( ). The Edit SOAP/XML Credential modal page appears.
  3. Enter values in the following fields:

Basic Settings

  • Profile Name. Type a new name for the credential.
  • URL. Type the URL for the AppDynamics account controller.
  • HTTP Auth User. Type the username of an AppDynamics user account that is assigned the "Applications and Dashboard Viewer" role in the AppDynamics portal.
  • HTTP Auth Password. Type the AppDynamics user account password.

SOAP Options

  • Embed Value [%1]. Type your AppDynamics account name

CURL Options

  • SSLCERT. Type the certificate path for your SSL certificate.
  • SSLVERIFYPEER. Leave the default value “1” so that the SSL configuration is enabled.
  1. Click the Save As button and then click OK.

Configuring an AppDynamics Device Template

A device template allows you to save a device configuration and apply it to multiple devices. The Cisco: AppDynamics PowerPack includes the "Cisco: AppDynamics Application Template." You must configure this device template to use the AppDynamics SOAP/XML credentials that you created.

If you configure this device template correctly, then when you align the "Cisco: AppDynamics Application Discovery" Dynamic Application to the AppDynamics account controller virtual device, SL1 will use the device template to automatically align the AppDynamics Dynamic Applications to each of the AppDynamics applications it discovers in your account.

The template includes the following Dynamic Applications:

  • Cisco: AppDynamics Tier Discovery
  • Cisco: AppDynamics Health Rule Violations
  • Cisco: AppDynamics Application Performance
  • Cisco: AppDynamics Backend Configuration

To configure the AppDynamics device template:

  1. Go to the Configuration Templates page (Devices > Templates, or Devices > Templates, or Registry > Devices > Templates in the classic SL1 user interface in the SL1 classic user interface).

  1. Locate the "Cisco: AppDynamics Application Template" and click its wrench icon (). The Device Template Editor page appears.
  2. Click the Dyn Apps tab. The Editing Dynamic Application Subtemplates page appears.

  1. Complete the following fields:
  • Template Name. Type a new name for the device template.
  • Credentials. Select the SOAP/XML credential that you created for AppDynamics.

  1. Click the next Dynamic Application listed in the Subtemplate Selection section on the left side of the page and then select the AppDynamics SOAP/XML credential in the Credentials field.
  2. Repeat step 5 until you have selected the AppDynamics SOAP/XML credential in the Credentials field for all of the Dynamic Applications listed in the Subtemplate Selection section.
  3. Click Save As.

You must rename the sample Cisco: AppDynamics Application Template and click Save As to save it. If you do not rename the device template, then your device template will be overwritten the next time you upgrade the Cisco: AppDynamics PowerPack.

Creating an AppDynamics Virtual Device

Because the AppDynamics account controller does not have a static IP address, you cannot discover it using a typical discovery session. Instead, you must create a virtual device that represents the account controller. A virtual device is a user-defined container that represents a device or service that cannot be discovered by SL1. You can use the virtual device to store information gathered by policies or Dynamic Applications.

To create a virtual device that represents your AppDynamics account controller:

  1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface.

  1. Click the Actions button and select Create Virtual Device from the menu. The Create Virtual Device modal page appears.

  1. Enter values in the following fields:
  • Device Name. Type a name for the device.

  • Organization. Select the organization for this device. The organization you associate with the device limits the users that will be able to view and edit the device. Typically, only members of the organization will be able to view and edit the device.
  • Device Class. Select Cisco Systems| AppDynamics Controller.
  • Collector. Select the collector group that will monitor the device.
  1. Click Add to create the virtual device.

Aligning the AppDynamics Dynamic Applications

The Dynamic Applications in the Cisco: AppDynamics PowerPack are divided into the following types:

  • Count. This Dynamic Application polls AppDynamics to determine the number of component devices monitored by SL1.

  • Discovery. These Dynamic Applications poll AppDynamics for new applications or changes to existing applications.
  • Configuration. These Dynamic Applications retrieve configuration information about each application and component device and retrieve any changes to that configuration information.
  • Performance. These Dynamic Applications poll AppDynamics for performance metrics.

Counting AppDynamics Component Devices

If you want to determine the number of AppDynamics component devices that will be monitored prior to running discovery (for instance, to estimate license usage), you can manually align the "Cisco: AppDynamics Component Count" Dynamic Application with the AppDynamics application controller virtual device.

To manually align the "Cisco: AppDynamics Component Count" Dynamic Application:

  1. Go to the Devices page.

  1. Locate the AppDynamics controller virtual device and click on it.
  2. In the Device Investigator page, click the Collections tab.
  3. Click Edit and then click the Align Dynamic App button. The Align Dynamic Application window appears.

  1. Click Choose Dynamic Application. The Choose Dynamic Application window appears.

  1. Select the "Cisco: AppDynamics Component Count" Dynamic Application and click Select. The name of the selected Dynamic Application appears in the Align Dynamic Application window.
  2. If a default credential is listed below the Dynamic Application and it is the credential you created for your AppDynamics device, skip ahead to step 10. Otherwise, uncheck the box next to the credential name.
  3. Click Choose Credential. The Choose Credential window appears.
  4. Select the credential you created for your AppDynamics device for the Dynamic Application and click the Select button. The name of the selected credential appears in the Align Dynamic Application window.
  5. Click the Align Dynamic App button. When the Dynamic Application is successfully aligned, it is added to the Collections tab, and a confirmation message appears at the bottom of the tab.

If your AppDynamics account has a large number of applications, tiers, or nodes, ScienceLogic recommends discovering your account on a Collector Group with a sufficient number of Data Collectors. For guidelines about the number of Data Collectors you might need, see the section on Hardware Requirements.

Counting AppDynamics Component Devices in the SL1 Classic User Interface

If you want to determine the number of AppDynamics component devices that will be monitored prior to running discovery (for instance, to estimate license usage), you can manually align the "Cisco: AppDynamics Component Count" Dynamic Application with the AppDynamics application controller virtual device.

To manually align the "Cisco: AppDynamics Component Count" Dynamic Application:

  1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).

  1. Locate the AppDynamics controller virtual device and then click its wrench icon ().
  2. In the Device Administration panel, click the Collections tab. The Dynamic Application Collections page appears.
  3. Click the Actions button and select Add Dynamic Application from the menu.

  1. In the Dynamic Application Alignment modal:
  • In the Dynamic Applications field, select Cisco: AppDynamics Component Count.
  • In the Credentials field, select the credential you created for AppDynamics.

  1. Click Save to align the Dynamic Application with the AppDynamics account controller virtual device.

If your AppDynamics account has a large number of applications, tiers, or nodes, ScienceLogic recommends discovering your account on a Collector Group with a sufficient number of Data Collectors. For guidelines about the number of Data Collectors you might need, see the section on Hardware Requirements.

Discovering AppDynamics Applications, Component Devices, and Databases

To discover all of the applications and components of your AppDynamics account, you must manually align the "Cisco: AppDynamics Application Discovery" Dynamic Application with the AppDynamics account controller virtual device.

To manually align the "Cisco: AppDynamics Application Discovery" Dynamic Application:

  1. Go to the Devices page, locate the AppDynamics controller virtual device, and click on it.
  2. In the Device Investigator, click the Collections tab.
  3. Click Edit and then click the Align Dynamic App button.

  1. In the Align Dynamic Application window, click Choose Dynamic Application. The Choose Dynamic Application window appears.

  1. Select the "Cisco: AppDynamics Application Discovery" Dynamic Application and click Select. The name of the selected Dynamic Application appears in the Align Dynamic Application window.
  2. If a default credential is listed below the Dynamic Application in the Align Dynamic Application window and it is the credential you created for your AppDynamics device, skip ahead to step 9. Otherwise, uncheck the box next to the credential name.
  3. Click Choose Credential. The Choose Credential window appears.
  4. Select the credential you created for your AppDynamics device for the Dynamic Application and click the Select button. The name of the selected credential appears in the Align Dynamic Application window.
  5. Click the Align Dynamic App button. When the Dynamic Application is successfully aligned, it is added to the Collections tab, and a confirmation message appears at the bottom of the tab.

If you are also monitoring databases, repeat the steps above to manually align the "Cisco: AppDynamics Database Events" and "Cisco: AppDynamics Database Service Discovery" Dynamic Applications.

When you align the "Cisco: AppDynamics Application Discovery" Dynamic Application with the AppDynamics controller virtual device, and if you have configured the AppDynamics device template correctly, then the following happens:

  • Events are triggered indicating that AppDynamics application virtual devices are being created for each application discovered in the AppDynamics account.
  • Those events trigger Run Book Actions that apply the AppDynamics device template to each of the application virtual devices
  • The device template aligns additional Dynamic Applications to each of the application virtual devices, which results in the creation of child component devices representing the tiers and nodes under those applications.

If the application virtual devices are not discovered when you align the "Cisco: AppDynamics Application Discovery" Dynamic Application to the AppDynamics account controller virtual device or if the application virtual devices are discovered but the Dynamic Applications aligned to those application virtual devices are using the incorrect credentials because the "Cisco: AppDynamics Application Template" Device Template was not modified to use your correct AppDynamics credentials, then you must delete all devices including the account controller virtual device and repeat the process again.

Discovering AppDynamics Applications, Component Devices, and Databases in the SL1 Classic User Interface

To discover all of the applications and components of your AppDynamics account, you must manually align the "Cisco: AppDynamics Application Discovery" Dynamic Application with the AppDynamics account controller virtual device.

To manually align the "Cisco: AppDynamics Application Discovery" Dynamic Application:

  1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).

  1. Locate the AppDynamics controller virtual device and then click its wrench icon ().
  2. In the Device Administration panel, click the Collections tab. The Dynamic Application Collections page appears.
  3. Click the Actions button and select Add Dynamic Application from the menu.

  1. In the Dynamic Application Alignment modal:
  • In the Dynamic Applications field, select Cisco: AppDynamics Application Discovery.
  • In the Credentials field, select the credential you created for AppDynamics.

  1. Click Save to align the Dynamic Application with the AppDynamics account controller virtual device.

If you are also monitoring databases, repeat the steps above to manually align the "Cisco: AppDynamics Database Events" and "Cisco: AppDynamics Database Service Discovery" Dynamic Applications.

When you align the "Cisco: AppDynamics Application Discovery" Dynamic Application with the AppDynamics controller virtual device, if you have configured the AppDynamics device template correctly, then the following happens:

  • Events are triggered indicating that AppDynamics application virtual devices are being created for each application discovered in the AppDynamics account.
  • Those events trigger Run Book Actions that apply the AppDynamics device template to each of the application virtual devices
  • The device template aligns additional Dynamic Applications to each of the application virtual devices, which results in the creation of child component devices representing the tiers and nodes under those applications.

If the application virtual devices are not discovered when you align the "Cisco: AppDynamics Application Discovery" Dynamic Application to the AppDynamics account controller virtual device or if the application virtual devices are discovered but the Dynamic Applications aligned to those application virtual devices are using the incorrect credentials because the "Cisco: AppDynamics Application Template" Device Template was not modified to use your correct AppDynamics credentials, then you must delete all devices including the account controller virtual device and repeat the process again.

Run Book Actions

The "Cisco: AppDynamics" PowerPack includes the “Cisco: AppDynamics Application Discovery” run book action which creates Cisco AppDynamics Application virtual devices, aligns Dynamic Applications by template, renames, and deletes AppDynamics applications. After a virtual device for an AppDynamics application is created, the run book action applies the AppDynamics device template to the application's virtual devices.

The “Cisco: AppDynamics Application Discovery” run book action can consider or ignore the SL1 Organization name when creating, renaming, or deleting the AppDynamics applications. You can enable or disable this option using the “Search Applications on all Organizations” Threshold, found in “Cisco: AppDynamics Application Discovery” Dynamic Application. This threshold is enabled by default.

ScienceLogic recommends you keep the threshold enabled only if you want to monitor AppDynamics applications across multiple organizations. Otherwise, disable the threshold if you want to monitor AppDynamics applications in the default organization that has the controller.

To disable the Search Applications on all Organizations Threshold:

  1. Go to Dynamic Applications Manager page (System>Mange>Dynamic Applications).
  2. Click on the wrench icon () of the “Cisco: AppDynamics Application Discovery” Dynamic Application.
  3. Go to the Threshold tab and click the wrench icon () of Search Applications on all Organizations threshold.
  4. Change the Threshold Value option to "0".
  5. Click Save.

Discovering Multiple AppDynamics Accounts

To discover multiple AppDynamics accounts, you must:

  1. Create a separate credential for each account, using a unique Profile Name for each credential.

  1. Create a separate device template for each account, using a unique Template Name and aligning the appropriate credential to the Dynamic Applications in each device template.
  2. Create a separate AppDynamics account controller virtual device for each account.
  3. Discover each account's applications and components.

Viewing Component Devices

When SL1 performs collection for your AppDynamics account, SL1 will create component devices that represent each device and align other Dynamic Applications to those component devices. Some of the Dynamic Applications aligned to the component devices will also be used to create additional component devices. All component devices appear in the Devices page just like devices discovered using the ScienceLogic discovery process.

In addition to the Devices page, you can view the AppDynamics account controller, applications, and all other component devices in the following places in the user interface:

  • The Device Investigator Map page (click Map in the Device Investigator page) displays a map of a particular device and all of the devices with which it has parent-child relationships. Double-clicking any of the listed devices reloads the page to make the selected device the primary device.

  • The Device Components page (Devices > Device Components) displays a list of all root devices and component devices discovered by SL1 in an indented view, so you can easily view the hierarchy and relationships between child devices, parent devices, and root devices. To view the component devices associated with an AppDynamics account, find the AppDynamics root device and click its plus icon (+):

  • The Component Map page (Classic Maps > Device Maps > Components) allows you to view devices by root node and view the relationships between root nodes, parent components, and child components in a map. This makes it easy to visualize and manage root nodes and their components. SL1 automatically updates the Component Map as new component devices are discovered. The platform also updates each map with the latest status and event information. To view the map for an AppDynamics account, go to the Component Map page and select the map from the list in the left NavBar. To learn more about the Component Map page, see the section on Views.

Viewing Component Devices in the SL1 Classic User Interface

When SL1 performs collection for your AppDynamics account, SL1 will create component devices that represent each device and align other Dynamic Applications to those component devices. Some of the Dynamic Applications aligned to the component devices will also be used to create additional component devices. All component devices appear in the Device Manager page just like devices discovered using the ScienceLogic discovery process.

In addition to the Device Manager page, you can view the AppDynamics account controller, applications, and all other component devices in the following places in the user interface:

  • The Device View modal page (click the bar-graph icon [] for a device, then click the Topology tab) displays a map of a particular device and all of the devices with which it has parent-child relationships. Double-clicking any of the devices listed reloads the page to make the selected device the primary device:

  • The Device Components page (Devices > Device Components) displays a list of all root devices and component devices discovered by SL1 in an indented view, so you can easily view the hierarchy and relationships between child devices, parent devices, and root devices. To view the component devices associated with an AppDynamics account, find the AppDynamics root device and click its plus icon (+):

  • The Device Component Map page (Classic Maps > Device Maps > Components) allows you to view devices by root node and view the relationships between root nodes, parent components, and child components in a map. This makes it easy to visualize and manage root nodes and their components. SL1 automatically updates the Device Component Map as new component devices are discovered. SL1 also updates each map with the latest status and event information. To view the map for an AppDynamics account, go to the Device Component Map page and select the map from the list in the left NavBar. To learn more about the Device Component Map page, see the section on Views.

Creating Device Relationships Between Nodes and Servers

If you want to create a device relationship between AppDynamics nodes and the physical servers where they reside, you must manually align the "Cisco: AppDynamics Node to Server Relationship" Dynamic Application to the physical server device. The "Cisco: AppDynamics Node to Server Relationship" Dynamic Application can create relationships between a single server and one or more nodes.

To manually align the "Cisco: AppDynamics Node to Server Relationship" Dynamic Application:

  1. Go to the Devices page, locate the AppDynamics physical server device, and click on it. In the Device Investigator, click the Collections tab.
  2. Click Edit and then click the Align Dynamic App button.

  1. In the Align Dynamic Application window, click Choose Dynamic Application. The Choose Dynamic Application window appears.

  1. Select the "Cisco: AppDynamics Node to Server Relationship" Dynamic Application and click Select. The name of the selected Dynamic Application appears in the Align Dynamic Application window.
  2. If a default credential is listed below the Dynamic Application in the Align Dynamic Application window and it is the credential you created for your AppDynamics device, skip ahead to step 9. Otherwise, uncheck the box next to the credential name.
  3. Click Choose Credential. The Choose Credential window appears.
  4. Select the credential you created for your AppDynamics device for the Dynamic Application and click the Select button. The name of the selected credential appears in the Align Dynamic Application window.
  5. Click the Align Dynamic App button. When the Dynamic Application is successfully aligned, it is added to the Collections tab, and a confirmation message appears at the bottom of the tab.
  6. To view the relationship, go to the Device Investigator Map page (click the Map tab) or the Component Map page (Classic Maps > Device Maps > Components) for the node device.

You must ensure that the server hostname matches the node machine name that is collected by the "Cisco: AppDynamics Node Configuration" Dynamic Application. If the physical server device name is an IP address or otherwise differs from the machine name collected by the "Cisco: AppDynamics Node Configuration" Dynamic Application, you can go to the server's Device Investigator page, click Edit, and edit the Device Name to match the node machine name.

Creating Device Relationships Between Nodes and Servers in the SL1 Classic User Interface

If you want to create a device relationship between AppDynamics nodes and the physical servers where they reside, you must manually align the "Cisco: AppDynamics Node to Server Relationship" Dynamic Application to the physical server device. The "Cisco: AppDynamics Node to Server Relationship" Dynamic Application can create relationships between a single server and one or more nodes.

To create device relationships between nodes and servers:

  1. Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface).

  1. Locate the AppDynamics physical server device and then click its wrench icon ().
  2. In the Device Administration panel, click the Collections tab. The Dynamic Application Collections page appears.
  3. Click the Actions button and select Add Dynamic Application from the menu.

  1. In the Dynamic Application Alignment modal:
  • In the Dynamic Applications field, select Cisco: AppDynamics Node to Server Relationship.
  • In the Credentials field, select the credential you created for AppDynamics.

  1. Click Save to align the Dynamic Application with the AppDynamics physical server device.
  2. To view the relationship, go to the Device View modal page (click the bar-graph icon [] for a device, then click the Topology tab) or the Device Component Map page (Classic Maps > Device Maps > Components) for the node device.

You must ensure that the server hostname matches the node machine name that is collected by the "Cisco: AppDynamics Node Configuration" Dynamic Application. If the physical server device name is an IP address or otherwise differs from the machine name collected by the "Cisco: AppDynamics Node Configuration" Dynamic Application, you can go to the server's Device Properties page (Devices > Classic Devices > wrench icon) and edit the Device Name to match the node machine name.