How do I configure the AppDynamics Service Graph Connector?
Current Version: 1.4
Sample Application Service to Monitor: MediaWiki
URL: http://10.197.203.204:5000/mediawiki
A 2-Tier PHP-based Web Application running on a 5 VM Node configuration in our Crucible Lab Environment will be used to demonstrate the AppDynamics Observability Service Graph Connector.
Environment:
HAProxy Load Balancer (ardeilmwadhap01) routes Web Requests to an Apache Web Server Cluster (ardeilmwadapp01, ardeilmwadap02, ardeilmwadapp03) that has the MediaWiki Application installed and running. The MediaWiki (PHP) Application in turn routes DB Requests to a MySQL Server DB (ardeilmwaddb01) as depicted in the below top-down discovered Application Service Map
This MediaWiki Application is being monitored by the AppDynamics SaaS cloud-based solution, where all application-component data with respect to the application is stored.
The following topics are covered in this How do I configure the AppDynamics Service Graph Connector? Article:
A. Set up Application to be monitored in AppDynamics Cloud
B. Analyze your Application in AppDynamics Cloud
C. Installing & Configuring AppDynamics Service Graph Connector on your ServiceNow Instance
D. Run AppDynamics Service Graph Connector Scheduled Data Import Jobs on your ServiceNow Instance
E. Analyze the Application Service Map created by the AppDynamics Service Graph Connector for your Application in your ServiceNow Instance
F. Analyze the CMDB Records created\updated by the AppDynamics Service Graph Connector for your Application in your ServiceNow Instance
G. Event Management
A. Set up Application to be monitored in AppDynamics Cloud
Unlike Dynatrace that has a single Agent, OneAgent, which is Technology agnostic(i.e. installed on all the VMs containing the Application to be monitored regardless of the Technology in use by the VMs), AppDynamics has Agents specific to the Technology Stack that the Application is running on. The instructions below include specific details for installing the AppDynamics Agent required for our sample MediaWiki Application.
Note: For the 3 ardeilmwadapp01, ardeilmwadap02, ardeilmwadapp03 VM's containing the Apache Web Servers the order in which these Agents are installed is important. Please install them in the Order indicated below.
(i) Log into your company's AppDynamics Cloud Instance
1. Apache Web Server Agent Installation - ardeilmwadapp01, ardeilmwadap02, ardeilmwadapp03 VM's
(ii) Install the Apache Web Server Agent as per the AppDynamics Install the Apache Agent documentation
(iii) Configure the Apache Web Server Agent by providing the following values for the appdynamics_agent.conf properties specified in the AppDynamics Configure the Apache Agent documentation ( 'appdynamics_agent.conf ' usually found in the '/etc/httpd/conf ' directory);
AppDynamicsEnabled ON
AppDynamicsControllerHost your AppDynamics Cloud Instance host name
AppDynamicsControllerPort 443
AppDynamicsControllerSSL ON
AppDynamicsAccountName your AppDynamics Account name
AppDynamicsAccessKey your AppDynamics Access Key
AppDynamicsApplication MediaWiki
AppDynamicsTier MediaWiki-WebTier
AppDynamicsNode ApacheWebServer@ardeilmwadapp0n (where n is 1, 2 or 3 depending on Apache Web Server VM)
AppDynamicsLaunchProxy ON
(iv) Configure the Apache Web Server to include the new appdynamics_agent.conf file on Startup by adding the below lines to the bottom of the httpd.conf Config File in the /etc/httpd/conf directory - Configure the Apache Server for AppDynamics
#Include AppDynamics Apache Agent Configuration
Include conf/appdynamics_agent.conf
(v) Restart the Apache Web Server
(vi) Execute the ps -ef | grep proxy command to confirm that the /opt/appdynamics-sdk-native/proxy Apache Web Server Agent process is running.
2. PHP Agent Installation - ardeilmwadapp01, ardeilmwadap02, ardeilmwadapp03 VM's
(vii) Install the PHP Agent as per the AppDynamics Install the PHP Agent documentation
(viii) Configure the PHP Agent by providing the following values for the appdynamics_agent.ini properties specified in the AppDynamics PHP Configuration Files documentation ('appdynamics_agent.ini' file usually found in the /etc/php.d/ or the /etc/php directory);
agent.controller.hostName = your AppDynamics Cloud Instance host name
agent.controller.port = 443
agent.applicationName = MediaWiki
agent.tierName = MediaWiki-FrontEnd
agent.nodeName = ardeilmwadapp0n (where n is 1, 2 or 3 depending on Apache Web Server VM)
agent.controller.ssl.enabled = 1
agent.accountName = your AppDynamics Account name
agent.accountAccessKey = your AppDynamics Access Key
(ix) Restart the Apache Web Server
(x) Execute the ps -ef | grep proxy command to confirm that the /usr/lib/appdynamics-php-agent/proxy PHP Agent process is running.
3. MySQL Agent Installation - ardeilmwaddb01 VM
(xi) Navigate to the Getting Started Tab in your AppDynamics Cloud Instance and click on the Getting Started Wizard button - Install the database agent
- Click on the Databases Tile
- Select MySQL from the Pulldown Menu
- Follow the Steps on the MySQL Installer Page to install the MySQL Agent on the ardeilmwaddb01 VM containing the MySQL DB Server
(xii) Navigate to theardeilmwaddb01VM Terminal Session
(xiii) Start the DB Agent by executing the following command:
java -jar /usr/sbin/db-agent.jar
Note: You can place a dbagent.service file like the one below in the /etc/system/systemd directory and execute the sudo systemctl enable dbagent.service command to enable the automatic startup of this DB Agent:
[Unit]
Description=Appd DB agent
After=network.target
[Service]
Type=simple
User=root
ExecStart=/bin/java -jar /usr/sbin/db-agent.jar
LimitNOFILE=40000
Restart=no
[Install]
WantedBy=multi-user.target
(xiv) Execute the ps -ef | grep db-agent command to confirm that the /usr/sbin/db-agent MySQL DB Agent process is running.
4. Machine Agent Installation - ardeilmwadapp01, ardeilmwadap02, ardeilmwadapp03 VM's
(xv) Install the Machine Agent as per the AppDynamics Install the Machine Agent documentation
(xvi) Configure the Machine Agent by providing the following values for the controller-info.xml properties specified in the Appdynamics Configure the Machine Agent documentation('controller-info.xml' file usually found in the '/opt/appdynamics/machine-agent/conf/' directory);
<controller-host>your AppDynamics Cloud Instance host name</controller-host>
<controller-port>443</controller-port>
<controller-ssl-enabled>true</controller-ssl-enabled>
<account-access-key>your Access Key</account-access-key>
<account-name>your Account Name</account-name>
<sim-enabled>true</sim-enabled>
(xvii) Start the Machine Agent by executing the following command:
sudo systemctl start appdynamics-machine-agent
(xviii) Execute the ps -ef | grep machineagent command to confirm that the /opt/appdynamics/machine-agent Machine Agent process is running.
Note: As part of the '(xv) Install the Machine Agent' Installation step above, an appdynamics-machine-agent.service Service file was installed in the /etc/system/systemd directory. This enables the automatic startup of the Machine Agent.
If you need to stop if for any reason, you can stop it by executing the following command:
sudo systemctl stop appdynamics-machine-agent
B. Analyze your Application in AppDynamics Cloud
(i) Send some Network Traffic through your Application. e.g. For our MediaWiki Application we hit the http://10.197.203.234:5000/mediawiki MediaWiki Web Application URL and sent various Web Requests through the Application Home Page (by clicking on different links on the page)
(ii) Navigate to the Applications Tab in your AppDynamics Cloud Instance Portal
(iii) Find your Application Tile amongst the Application Tiles Displayed in the Applications Tab, e.g. MediaWiki and click on it
(iv) If your Application has been setup for Monitoring correctly in AppDynamics Cloud Instance and enough Network Traffic has been detected by AppDynamics for your Application you will see an Application Flow Map depicting the following for your application:
- Infrastructure Services in use in your Application environment depicted as Application Tiers with Connection lines between them. These will be the Application Tiers that you configured for each of the Application Agents that you installed. Each Application Tier is represented as a circle with the number of Nodes within the Tier indicated in the center of the circle. An Application Tier can be thought of as a collection of Application Instances with the Nodes within the Application Tier representing each Individual Application Instance.
- Database Instances that may be in your application environment with Connection lines between the them and the Application Tier(s) connecting to them.
- Message Queues that that may be in your application environment with Connection lines between the them and the Application Tier(s) connecting to them.
The screenshot below shows the Application Flow Map for our MediaWiki Application in the Crucible Lab Environment.
The diagram shows 2 Application Tiers, the Media-WebTier Tier connecting to the Media-FrontEnd Tier that was configured for the Apache Web Server Agent and the PHP Agent respectively (the Agents monitoring our MediaWiki application). Media-WebTier is the name that was specified for the AppDynamicsTier property in step (iii) of the 1. Apache Web Server Agent Installation section above while Media-FrontEnd is the name that was specified for the agent.tierName property in step (viii) of the 2. PHP Agent Installation section above.
Each Application Tier is shown having 3 Nodes that were configured for each of the Apache Web Server and PHP Agents installed on the 3 ardeilmwadapp01, ardeilmwadap02, ardeilmwadapp03 VM's.
The MediaWiki-FrontEnd Tier is shown connecting to the MySQL Database Instance running on the ardeilmwaddb01 VM.
Application Tiers
For each of your Application Tiers click on its circle to get more detail on the Nodes contained within the Tier and the Servers that these Nodes run on, e.g. the MediaWiki-WebTier and MediaWiki-FrontEnd Application Tier circles for the MediaWiki Application shown above.
MediaWiki-WebTier Tier
The screenshot below shows the 3 Nodes that were configured for the MediaWiki-WebTier Application Tier where ApacheWebServer@aredeilmwadapp01, ApacheWebServer@aredeilmwadapp02 and ApacheWebServer@aredeilmwadapp03 were the Node Names specified for each of the 3 Apache Web Server Agents (AppDynamicsNode property) in step (iii) of the 1. Apache Web Server Agent Installation section above.
The screenshot below shows the 3 Linux Server's that the 3 Apache Web Server Nodes run on.
MediaWiki-FrontEnd Tier
The screenshot below shows the 3 Nodes that were configured for the MediaWiki-Front End Application Tier where aredeilmwadapp01, aredeilmwadapp02 and aredeilmwadapp03 were the Node Names specified for each of the 3 PHP Agents (agent.nodeName property) in step (viii) of the 2. PHP Agent Installation section above.
The screenshot below shows the 3 Linux Server's that the 3 PHP Nodes run on (same Servers that the 3 Apache Web Server Nodes run on).
Database Instances
For each of your Database Instances click on it's circle to get more detail on the calls made to the Database from the connecting Application Tier. The below screenshot shows details for the calls made to the MySQL wikidatabase from the MediaWiki FrontEnd Tier for the MediaWiki Application.
MySQL wikidatabase DB
C. Installing & Configuring AppDynamics Service Graph Connector on your ServiceNow Instance
(i) Login to your ServiceNow Instance
(ii) Install the following Applications & Plugins in the order shown:
Applications
- *Observability Commons for CMDB: sn_observability
- Integration Commons for CMDB: sn_cmdb_int_util
- CMDB CI Class Model: sn_cmdb_ci_class
- ITOM Discovery License: com.snc.itom.discovery.license (Included with full Discovery Product)
- Event Management: sn_em_ai (for enabling the capturing of events from AppDynamics)
- Service Graph Connector for Observability - AppDynamics: sn_sg_appd
*It's important that Observability Commons for CMDB is installed before Service Graph Connector for Observability AppDynamics. This is required in order for you to see the Push HTTP Request Template step in the Configure API Authentication Section of Guided Setup. This step is explained in greater detail in the Event Management Section at the end of this Whitepaper.
Plugins
7. com.glide.hub.action_type.datastream Plugin (ServiceNow IntegrationHub Action Template - Data Stream) - click on the Request Plugin Button from the System Applications Screen
(iii) Navigate to Setup under SG Connector Observability - AppDynamics in the Filter Menu
(iv) Go through all Setup Steps as per the ServiceNow Documentation: Configure Service Graph Connector for Observability - AppDynamics
Configure API Authentication
In the Configure the Connection Section, in order to execute the 3rd Push HTTP Request Template Step, the User that you provided in the 1st Configure the Connection Step of this section will need to have the HTTP Request Template Role assigned to their User Account in AppDynamics. If this Role is not assigned to the User specified in the Configure the Connection Step, you will get an error message.
Advanced Settings
In the Advanced Settings Section, turn on the Toggle to populate relationships between tiers checkbox. Turning on this checkbox ensures that the CI Relationships[cmdb_ci_rel] Table is populated with the Application Tier Parent Child Relationship records needed for populating the MediaWiki Application Service Map (created at the end of the AppDynamics Scheduled Import Jobs).
e.g. MediaWiki-WebTier-TIER-servicenow-prod.saas.appdynamics.com-1661849 (Parent) Depends on:UsedBy ApacheWebServer@ardeilmwadapp01 (Child)
D. Run AppDynamics Service Graph Connector Scheduled Data Import Jobs on your ServiceNow Instance
(i) Navigate to Scheduled Data Imports under SG Connector Observability - AppDynamics in the Filter Menu. 4 Scheduled Import Jobs should be listed as shown below:
(ii) Open the SG-AppDynamics Servers and Applications Parent Scheduled job record and click on the Execute button
(iii) Navigate to Concurrent Import Sets in the Filter Menu.
- Wait for all 4 Scheduled Data Import jobs to finish
For each Scheduled Data Import Job, the following happens:
- Payload Records are created in the appropriate Scheduled Data Import Staging Table with data that is loaded from the Scheduled Data Import Data Source.
- These Payload Records are then passed to the Robust Import Set Transformer associated with the Scheduled Data Import Data Source which in turn Transforms their data as defined by the Robust Import Set Transformer Transform Definition (using the Robust Transform Engine(RTE) ).
- Output Records from the Robust Import Set Transformer are then sent to the Identification & Reconciliation(IRE) Engine for processing.
- The Identification & Reconcilation(IRE) Engine does the following with each Output Record:
- It Creates\Updates the appropriate CI Record in the CMDB
- It Creates a Source Record with Key CI Record data like Source Native Key, Configuration Item and Target Table (CI Type) in the Sources[sys_object_source] Table so that these CI's can be quickly located at a later point when needed, like e.g. during AppDynamics Event Processing (described further down in the G. Event Management Section below).
E. Analyze the Application Service Map created by the AppDynamics Service Graph Connector for your Application in your ServiceNow Instance
(i) Navigate to Application Services under Service Mapping in the Filter Menu.
(ii) Click All to show All Application Service Types
You should see a Calculated Application Service for your Application with the following format: Application Name-APPLICATION-XXXXXXXXXX, e.g. MediaWiki-APPLICATION-servicenow-prod.saas.appdynamics.com-1089624 for the MediaWiki Calculated Application Service that was automatically generated at the end of the Scheduled Data Import.
(iii) Click on the View Map button to the right of your Calculated Application Service, e.g. MediaWiki-APPLICATION-servicenow-prod.saas.appdynamics.com-1089624 in the case of our MediaWiki Application.
An Application Service Map Page should be displayed showing the Service Map for your Application. In the case of our MediaWiki Application the MediaWiki Application Service Map depicts 2 separate Entry Points (shown in the screen shot below), 1 for each Application Tier associated with your Application (Application Tiers explained in step (iv) of the Analyze your Application in AppDynamics Cloud Section above)
- MediaWiki-WebTier-TIER-servicenow-prod.saas.appdynamics.com-1661849
Processes incoming Web Requests from the http://10.197.203.234:5000/mediawiki URL (hosted on the HAProxy Load Balancer).
- MediaWiki-FrontEnd-TIER-servicenow-prod.saas.appdynamics.com-1661881
Receives the Web Requests being routed to it from the MediaWiki-WebTier Tier.
Note: A HAProxy Load Balancer Entry Point is not shown as a separate Entry because AppDynamics does not classify HAProxy Load Balancer as a separate Tier\Service (i.e. No AppDynamic Agent specific to the HAProxy Load Balancer Application).
(iv) For every Application Tier associated with your Application in AppDynamics, a Calculated Application Service record is created in the ServiceNow CMDB to represent that Tier and uses the Tier Name-TIER-XXXXXXXXXX naming convention for the Calculated Application Service Name. The screenshot below shows all the TIER type Calculated Application Service CI records that were created in the Calculated Application Service[cmdb_ci_service_calculated] table to represent the Tiers associated with the MediaWiki Application. These records were created at the end of the AppDynamics Service Graph Connector Scheduled Job Imports.
All these TIER type Calculated Application Services are represented as Contained Application Services in your Application's Service Map. e.g. MediaWiki-APPLICATION-servicenow-prod.saas.appdynamics.com-1089624. The Root Application Service Map shows the Contained Application Service(s) with the Service Map for the Services that it is dependent on being shown in a new Window when you select Show Contained Service in its Pull Down Menu.
For example, for the MediaWiki Application, below is a screen shot showing the Service Map for the MediaWiki-WebTier-TIER-servicenow-prod.saas.appdynamics.com-1661849 Service Contained within the Outermost MediaWiki-APPLICATION-servicenow-prod.saas.appdynamics.com-1089624 Root Service Map (shown in the screen shot in step (iii) above).
There are 3 separate Entry Points, 1 for each Node in the MediaWiki-WebTier Application Tier:
- ApacheWebServer@ardeilmwadapp01
- ApacheWebServer@ardeilmwadapp02
- ApacheWebServer@ardeilmwadapp03
Note: These are the Node Names displayed in the AppDynamics Cloud Instance Portal for the MediaWiki-WebTier Tier (as described in step (iv) of the Analyze your Application in AppDynamics Cloud Section above)
The screenshot below shows the Service Map for the MediaWiki-FrontEnd - TIER-servicenow-prod.saas.appdynamics.com-1661881 Service Contained within the Outermost MediaWiki - APPLICATION-servicenow-prod.saas.appdynamics.com-1089624 Root Service Map (shown in the screen shot in step (iii) above).
There are 3 separate Entry Points, 1 for each Node in the MediaWiki-FrontEnd Application Tier:
- ardeilmwadapp01
- ardeilmwadapp02
- ardeilmwadapp03
Note: These are the Node Names displayed in the AppDynamics Cloud Instance Portal for the MediaWiki-FrontTier Tier (as described in step (iv) of the Analyze your Application in AppDynamics Cloud Section above)
F. Analyze the CMDB Records created\updated by the AppDynamics Service Graph Connector for your Application in your ServiceNow Instance
(i) Navigate to cmdb_ci.list in the Filter Menu
(ii) Group by Discovery Source
(iii) Navigate to the SG-AppDynamics Discovery Source and double click on its Discovery source:SG-AppDynamics(n) link where n represents the Number of CMDB records(entities) Created\Updated by the AppDynamics Service Graph Connector.
--> All CMDB CI Records that were created\updated by the AppDynamics Service Graph Connector are listed.
(iv) Group By Class
A List of CMDB CI Records Created\Updated by the AppDynamics Service Graph Connector will be displayed grouped by Class.
- All the Tier entities associated with your Application in AppDynamics will be represented as Calculated Application Service Class Records
- All the Node entities associated with your Application in AppDynamics will be represented as Application Class Records in the Class List that is displayed
- All Server entities associated with your Application in AppDynamics will be represented as Server Class Records in the Class List that is displayed.
All Entities that are in turn associated with these Server Class records will be shown in the Class List displayed, e.g. IP Address, Network Adapter
The screen shot below shows all the Class Records displayed in this Class List for our MediaWiki Application.
G. Event Management
A SGO-AppDynamics Push Connector is installed as part of the Service Graph Connector for Observability - AppDynamics installation in the Push Connectors[sn_em_connector_listener] Table on your Instance. This Listener connector listens for Event Messages from your AppDynamics Source. These Events are sent from AppDynamics to your ServiceNow Instance via the EM-Connector Inbound Event REST API using the format
https://{Instance-name}.service-now.com/api/sn_em_connector/em/inbound_event?source=SGO-AppDynamics. The Listener connector parses the data from the Event Messages it receives and does the following:
- Constructs a Source Native Key (SourceNativeKey) from the controllerUrl + "|" + entity.entityTypeDisplayName + "|" + entity.id values that it receives in the Event Message Payload.
- Locates the CI associated with the Event by querying the Sources[sys_object_source] Table using this Source Native Key (Primary Key in the Sources[sys_object_source] Table).
- Creates an Event Record and populates the Configuration Item(sys Id) and Configuration Item Type fields in the Event Record with the output from this query (Binds the CI to the Event).
These Events are then processed by the Event Management Module on your ServiceNow Instance with Alerts being generated for these Events.
Event Management Configuration
Configuration is required at both the AppDynamics Cloud Instance side and the ServiceNow Instance side in order to enable AppDynamics to push the AppDynamics Events associated with your Application Infrastructure to your ServiceNow Instance.
ServiceNow Setup
Follow the steps below for Event Management setup in ServiceNow:
(i) Navigate to the Configure API authentication section in AppDynamics Guided Setup
(ii) Navigate to the Push HTTP Request Template step in this section
(iii) Click on the Create HTTP Request Template Form link on the AppDynamics HTTP Request Template Form that is displayed
Clicking on this Create HTTP Request Template Form link calls an AppDynamics API that in turn creates a new HTTP Request Template e.g. ServiceNowEMConnector-SN Instance Name.servicenow.com with your ServiceNow Instance Metadata (URL etc) in your AppDynamics Cloud Instance. This is part of the setup needed to enable AppDynamics to push AppDynamics Events to your ServiceNow Instance (via the the ServiceNow Event Management API). You will be selecting this new HTTP Request Template later on in the AppDynamics Setup section below.
AppDynamics Setup
Follow the steps below for Event Management setup in AppDynamics as per the Appdynamics Alert & Respond documentation:
(i) In your AppDynamics Cloud Instance Portal navigate to the Alert & Respond Tab
(ii) Select your Application, e.g. MediaWiki in the Application pulldown menu on this Tab.
(iii) Select Policies in the Left Hand Navigator of this Tab to bring up the Policies Screen.
(iv) Click on the +Create Button from the Action Bar shown at the top of this Policies screen to bring up a Create Policy screen that you will be using for creating a new AppDynamics Event Policy for your Application. The below screenshot shows the Create Policy Screen you can expect to see when you click on this +Create Button:
(v) Enter a Policy Name in the Name field on this screen e.g. MediaWiki Policy
(vi) From the list of Health Events displayed in this screen select the Health Events that you are interested in for your application, e,g Server Crashes
(vii) Navigate to the Actions Tab on the Create Policy Screen to bring up an Action Screen that you will be using to create a New Action for your Policy. The below screenshot shows the Action Screen that you can expect to see when you navigate to the Actions Tab.
(viii) Click on the + Button shown in the above screen shot to bring up the Select Action screen like the one shown in the below screen shot:
(ix) Click on the +Create Button on the Select Action Screen. A Create Action screen like the one shown below will be displayed to allow you to create a new Action to associate with the Policy you are in the process of creating for your Application
(x) Select the Make an HTTP Request radio button on the Create Action screen to bring up the below Create HTTP Action Dialog box.
Name: Specify a name for the new HTTP Action like e.g. Send MediaWiki Events to SN Instance Name
HTTP Request Template: Select the HTTP Request Template that you pushed to AppDynamics for your ServiceNow Instance (in Step (iii) of the above ServiceNow Setup section e.g. ServiceNowEMConnector-SN Instance Name.servicenow.com) from the HTTP Request Template Pulldown Menu.
(xi) Click on the Save Pushbutton to save the new HTTP Action e.g. Send MediaWiki Events to SN Instance Name
- This new HTTP Action will be associated with your new Application Policy
(xii) Click on the Save Pushbutton on the Create Policy Screen to save your new Application Policy.
The Application Policy screenshot below shows the Application Policy that was created for our MediaWiki Application:
The HTTP Request Template screenshot below shows the HTTP Request Template that was pushed to AppDynamics for our ServiceNow Instance:
AppDynamics is now enabled to push any Events associated with your Application to your ServiceNow Instance by calling the ServiceNow Event Management API any time these Events occur. These Events then get processed by the Event Management Module in your ServiceNow Instance with Alerts being created as appropriate etc. These Alerts then get shown in the AppDynamics Calculated Service Map similarly to how Alerts from other Monitoring Tools(e.g. Agent Client Collector) get shown when you click on Monitor Service on the Service Map. The screen shot below shows a Critical Alert being displayed for the ardeilmwadapp01 Linux Server on the MediaWiki-FrontEnd-TIER-servicenow-prod.saas.appdynamics.com-1661881 Service Map for the MediaWiki Application
Hi Prabhjyot,
Did you try searching for SGO-AppDynamics in the push connectors [sn_em_connector_listener] Table as oppose to SG-AppDynamics ?
The screenshot below shows the full name of the AppDynamics Push Connector that you should expect to see in this table:
If you still can't find it, I'd suggest checking that the *Observability Commons for CMDB: sn_observability Framework called out in Step 1 of the C. Installing & Configuring AppDynamics Service Graph Connector on your ServiceNow Instance section above was installed before the AppDynamics Service Graph Connector.
If you discovered that this Framework was not installed, you can still install it after the AppDynamics Service Graph Connector installation where you run Repair on the AppDynamics Service Graph Connector install to resolve any missing ServiceNow Table entries
Hoping this helps,
Thanks,
Anne-Marie
