Configure Service Graph Connector for Observability - AppDynamics using the guided setup

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 12 min. de leitura

    • Set up scheduled import jobs to pull in data from AppDynamics into your Configuration Management Database (CMDB).

    Antes de Iniciar

    Importante:
    Unless there are configuration issues, use SGC Central to configure the connection. The guided setup method for configuration is being deprecated.

    To use this Service Graph Connector, you need a subscription to a Subscription Unit that is based in the IT Operations Management (ITOM) Visibility application or in the ITOM Discovery application. As defined in the section titled "Managed IT Resource Types" in ServiceNow Subscription Unit Overview for your subscription, for managed IT resources that are created or modified in the CMDB by this Service Graph Connector, but that aren’t yet managed by ITOM Visibility or ITOM Discovery, these resources will increase Subscription Unit consumption from that application. Review your current Subscription Unit consumption within ITOM Visibility or ITOM Discovery to ensure available capacity.

    Dependencies and requirements:
    • The Integration Commons for CMDB store app, which is automatically installed.
    • The CMDB CI class models store app, which is automatically installed. See CMDB CI Class Models app.
    • The ITOM Discovery License plugin (com.snc.itom.discovery.license). You must activate this plugin.
    • ITOM Licensing plugin (com.snc.itom.license). For more information, see Request Discovery.
    • The Datastream Action plugin (com.glide.hub.action_type.datastream), which is automatically installed.
    • Observability Commons for CMDB (sn_observability), which is only required for event ingestion. This must be installed prior to installing the connector for Event Management to work. For more information, see Observability Commons for CMDB on the ServiceNow Store.
    When using client credentials for authentication, obtain the OAuth credentials from your AppDynamics administrator. Make a note of the following details:
    • Application (client) ID
    • Client Secret
    Nota:
    If you have an earlier version of the Service Graph Connector for Observability - AppDynamics, then do not migrate data from the old connector. You must uninstall the previous version and run the new integration.

    Role required: admin

    Role required: SGC-Admin (sn_cmdb_int_util.sgc_admin) or admin
    Nota:
    The admin user role is required to run background scripts and to provide access to global tables to the SGC-Admin user. For information about the user roles for Service Graph Connectors, see Service Graph Connector user roles.

    Procedimento

    1. Navigate to All > Service Graph Connector AppDynamics > Setup.
    2. Ensure that the application scope is set to the Service Graph Connector for Observability - AppDynamics application by using the application picker.
      For more information, see Application picker.
    3. Navigate to All > Service Graph Connectors > AppDynamics > Setup.
    4. On the Getting started page, select Get Started.
    5. Configure the authentication credentials and establish an HTTP connection to send requests to the AppDynamics API.
      1. In the Configure API authentication section of the Service Graph Connector for Observability - AppDynamics page, select Get Started.
      2. Configure the connection for AppDynamics by editing the default connection.

        You can configure either a Basic Auth connection or an OAuth connection.

        Nota:
        As the connector supports only single instance, edit the AppDynamicsConnectionAlias connection, available by default.
        • Configure a Basic Auth connection.
          1. For the Configure Basic Auth Connection task, select Configure.
          2. Select Edit for AppDynamicsConnectionAlias.
            Nota:
            If not redirected to the connection setup, search for AppDynamicsConnectionAlias on the Integrations page, and then select View Details to edit the default connection.
          3. In the Connection Information section of the Edit Connection window, fill in the fields.
            Tabela 1. Connection Information
            Field Description
            Connection name Name to identify the AppDynamics connection record.

            AppDynamicsConnectionAlias is the default credential alias name and is read-only.
            Host name Host name of your AppDynamics controller.
          4. (Optional) If a MID Server is required for the AppDynamics server connection, select the Use MID server check box. Then, select the MID Server-related fields accordingly.
          5. In the Credential Information section of the Edit Connection window, fill in the fields.
            Tabela 2. Credential Information
            Field Description
            Username AppDynamics account user name that is used to authenticate the connection request.
            Nota:
            Verify that Server Visibility is active for the AppDynamics account and the AppDynamics user has the Applications and Dashboards Viewer (Default) and Server Monitoring User (Default) roles.
            Password Password that is used to authenticate the connection request.
          6. Select Edit Connection.
          7. Return to the guided setup page.
          8. Set the Configure Basic Auth Connection task to complete by selecting Mark as Complete.
        • Configure an OAuth connection.
          1. For the Configure OAuth Authentication: Client Credentials task, select Configure.
          2. Select Edit for AppDynamicsConnectionAlias.
            Nota:
            If not redirected to the connection setup, search for AppDynamicsConnectionAlias on the Integrations page, and then select View Details to edit the default connection.
          3. In the Connection Information section of the Edit Connection window, fill in the fields.
            Tabela 3. Connection Information
            Field Description
            Connection name Name to identify the AppDynamics connection record.

            AppDynamicsConnectionAlias is the default credential alias name and is read-only.
            Connection URL Base URL of your AppDynamics controller.
          4. (Optional) If a MID Server is required for the AppDynamics server connection, select the Use MID server check box. Then, select the MID Server-related fields accordingly.
          5. In the Credential Information section of the Edit Connection window, fill in the fields.
            Tabela 4. Credential Information
            Field Description
            OAuth Client ID Application (client) ID of your AppDynamics client application as noted in the Before you begin section.
            Nota:
            Verify that the API client has a role with the required privileges and sufficient Token Expiration Time.
            OAuth Client Secret Client secret of your AppDynamics client application as noted in the Before you begin section.
          6. Select Edit Connection.
          7. Return to the guided setup page.
          8. Set the Configure OAuth Authentication: Client Credentials task to complete by selecting Mark as Complete.
      3. Configure the connection for AppDynamics by editing the default connection.
        Nota:
        As the connector supports only single instance, edit the AppDynamics Connection connection, available by default.
        1. For the Configure the connection task, select Configure.
        2. Select Edit for AppDynamics Connection.
          Nota:
          If not redirected to the connection setup, search for AppDynamics Connection on the Integrations page to edit the default connection.
        3. In the Connection Information section of the Edit Connection window, fill in the fields.
          Tabela 5. Connection Information
          Field Description
          Connection name Name to identify the AppDynamics connection record.

          AppDynamics Connection is the default credential alias name and is read-only.
          Host name Hostname of your AppDynamics controller.
          Nota:
          This field is automatically set to the URL to connect to the application. Leave the field value as is.
        4. (Optional) If a MID Server is required for the AppDynamics server connection, select the Use MID Server check box. Then, select the MID Server-related fields accordingly.
        5. In the Credential Information section of the Edit Connection window, fill in the fields.
          Tabela 6. Credential Information
          Field Description
          User name AppDynamics account user name that is used to authenticate the connection request.
          Nota:
          Verify that Server Visibility is active for the AppDynamics account and the AppDynamics user has the Applications and Dashboards Viewer (Default) and Server Monitoring User (Default) roles.
          Password Password that is used to authenticate the connection request.
        6. Select Edit Connection.
        7. Return to the guided setup page.
        8. Set the Configure the connection task to complete by selecting Mark as Complete.
      4. Test the connection.
        1. For the Test connection task, select Configure.
        2. Select the Test Connection related link to start the testing process.
        3. When the Status field is set to Success, return to the guided setup page.
          Nota:
          If any of the tests have errors, follow the suggestions for remediation.
        4. Set the Test the connection task to complete by selecting Mark as Complete.
      5. Enable AppDynamics event integration with your ServiceNow instance by pushing a default HTTP Request Template to AppDynamics.
        Nota:
        To push HTTP requests, verify that the Observability Commons for CMDB application (sn_observability) is installed for events ingestion on your ServiceNow instance. Also, on your AppDynamics instance, as the ServiceNow user, you must have the account-level Configure HTTP Request Templates permission to create or modify HTTP Request Templates.
        1. For the Push HTTP Request Template task, select Configure.
        2. Select the Push HTTP Request Template related link.
        3. Return to the guided setup page.
        4. Set the Push HTTP Request Template task to complete by selecting Mark as Complete.

        After you push the HTTP request template, multiple API calls are executed to start the event ingestion service in AppDynamics. For more information, see the Service Graph Connector for Observability AppDynamics article on the ServiceNow Community site.

      6. In the Configure Credentials section, configure your credentials.
        1. Select Configure.
        2. Update the Name and User name field.
          Nota:
          Server Visibility needs to be active for your AppDynamics account. The AppDynamics user requires the AppDynamics role: Applications and Dashboards Viewer (Default) and Server Monitoring User (Default).
        3. Click Update then Mark as Complete.
      7. In the Configure Connection section, configure the connection.
        1. Click Configure.
        2. Review the fields and enter the controller base URL into the Host field.
          Tabela 7. HTTP(s) Connection form
          Field Description
          Name Name of the connection.
          Host Target host value used by the connection. The Connection URL will automatically fill in the hostname.
          Credential Credential value that is used by this connection.
          Connection alias Connection value that is used to refer to the connection.
          URL builder URL builder that is used to build the connection URL.
          Connection URL Connection URL for the connection. You can either manually enter a URL, or use the URL builder to build the connection string.
          Mutual authentication Option to set the connection with mutual authentication.
          Protocol Underlying protocol used by the connection.
          Nota:
          Update the Protocol field if you are using anything other than https.
          Active Option to activate the HTTP connection.
          Domain Domain that contains the connection.
          Override default port Target value port that is used by the connection.
          Base path Base path for HTTPs connection.
        3. Click Update then Mark as Complete.
      8. In the Validate data sources section, validate the data sources by selecting Configure.
        1. Review the fields on the form.
          Tabela 8. Data Source form
          Field Description
          Name Unique name of this data source.
          Import set table label Label of the import set table that this data source will produce.
          Import set table name Name of the table that will be created for this data source.
          Type Data storage type of the data to be imported.
          Data in single column Option to set the data in a single column.
          Application Application that contains this record.
          Data Loader Script that loads data in the import set table.
        2. To test the connection, click the Test Load 20 Records related link.

          When the test is finished, select Mark as Complete.

          Testing the connection may take a few moments. The page is refreshed to show the test results.

          Nota:
          The connection is successful if the HTTP Status is 200. If there is anything displayed in the Error Code and Error Message fields, then the connection failed and further troubleshooting is required.
      9. In the Push HTTP Request Template section, push the HTTP Request by selecting Configure.
        Nota:
        To push HTTP requests, ensure that the Observability Commons for CMDB (sn_observability) plugin is installed for events ingestion on your ServiceNow instance. Also, on your AppDynamics instance, as the ServiceNow user, you must have the account-level Configure HTTP Request Templates permission to create or modify HTTP Request Templates.
        1. In the Related Links section, click Push HTTP Request Template.
        2. Click Mark as Complete.
        After you push the HTTP request template, multiple API calls are executed to start the event ingestion service in AppDynamics. For more information, see the Service Graph Connector for Observability AppDynamics article on the ServiceNow Community site.
    6. Configure duplicate detection rules.
      1. For the Configure duplicate detection rules task in the Duplicate detection rules section, select Configure.
      2. In the CMDB Duplicate Row Rules list, set the Active column value for a rule to true to activate the rule.
        Nota:
        To remove fields from being evaluated, add the field names in the Ignore Fields column for a rule. To ignore multiple fields, separate the fields with commas.
      3. Return to the guided setup page.
      4. Set the Configure duplicate detection rules task to complete by selecting Mark as Complete.
    7. Configure duplicate detection rules.
      1. On the left side bar, select the Configure duplicate detection rules icon (Duplicate rules icon.).
      2. On the Service Graph Connector for Observability - AppDynamics page, in the Duplicate detection rules section, select the task Configure duplicate detection rules.
      3. On the next page, in the Configure duplicate detection rules section, click Configure.
      4. On the CMDB Duplicate Row Rules form, select the rule that you want to activate and update the Active column value to true.
        Nota:
        To remove fields from being evaluated, add the field names in the Ignore Fields column. To ignore multiple fields, separate the fields with a comma in a separated list.

        When you're finished, click Mark as Complete.

    8. Configure advanced settings.
      1. For the Advanced Settings task in the Advanced section, select Configure.
      2. Review and modify the advanced properties.
        Tabela 9. Advanced properties
        Property Description
        Toggle to populate relationships between tiers Option to enable the import of relationships between AppDynamics tiers in the CI Relationship [cmdb_rel_ci] table.
        The number of minutes of metrics to fetch in order to generate tier to tier relationships Number of minutes of metrics to fetch for generating tier-to-tier relationships. For example, 60 retrieves the last hour's relationships.
        Toggle to import business transactions from AppDynamics Option to enable the import of business transactions into the Calculated Application Service [cmdb_ci_service_calculated] table.
        Toggle to populate tags for imported servers Option to enable the import of server tags into the Key Value [cmdb_key_value] table.
        Toggle to import node data from AppDynamics and map to the cmdb_ci_appl hierarchy Option to enable the import of nodes into the Application [cmdb_ci_appl] table hierarchy.
      3. Select Save.
      4. Set the Advanced Settings task to complete by selecting Mark as Complete.
    9. Configure advanced settings.
      1. On the left side bar, click the advanced icon (Advanced icon.).
      2. On the Service Graph Connector for Observability - AppDynamics page, in the Advanced section, select the task Advanced Settings.
      3. In the Advanced Settings section, click Configure.
        1. Review the set of advanced properties.
          Tabela 10. Advanced properties
          Advanced property Description
          Toggle to populate relationships between tiers The relationships between tiers will be imported in cmdb_rel_ci.
          Toggle to import business transactions from AppDynamics The business transactions will be imported into cmdb_ci_service_calculated.
          Toggle to populate tags for imported servers The server tags will be imported into cmdb_key_value.
          Toggle to import node data from AppDynamics and map to the cmdb_ci_appl hierarchy The nodes will be imported into cmdb_ci_appl table hierarchy.

          The performance impact changes based on the selected advanced setting.

        2. Select the Yes check box to activate each property, as needed.
        3. Click Save then Mark as Complete.
    10. Set up the SG-AppDynamics Servers and Applications scheduled job available by default.
      1. For the Configure scheduled job task in the Set up scheduled import jobs section, select Configure.
      2. On the Scheduled Data Import form, verify the field values for the SG-AppDynamics Servers and Applications scheduled job and select the Active check box.

        For more information, see Schedule a data import.

      3. Select Update.
      4. Set the Configure scheduled job task to complete by selecting Mark as Complete.