How  do I configure the Dynatrace Service Graph Connector using SGC Central with a Focus on Cloud Discovery?

 

Version : 1.16

Sample Azure Cloud Service Account:  az-itxlab1

Sample Azure VM:  az-itxlab1-east-lin-vic2

Sample AWS Cloud Service Account:  monitor 698091055457

Sample AWS EC2 Instance : DFOUND_Eng_org2_east2_vpc1_win_tomcat

Sample Kubernetes Cluster : otel-demo-on-k3s

Sample Kubernetes Pod : accounting-58c9b7d6b5-wtdx7

Ingesting Dynatrace Events(Yes\No): No

Tags ingested into CMDB(Yes\No): Yes

Filtering Applied(Yes\No): No

 

The focus of this Article is on analyzing the data brought in by the Dynatrace Service Graph Connector for the following Cloud Environments:

• Azure
• AWS
• Kubernetes

 

The following topics are covered in this  How do I configure the Dynatrace Service Graph Connector using SGC Central with a Focus on Cloud Discovery?  Article:

 

A. Set up Cloud Resources to be monitored in Dynatrace Cloud

B. Analyze your Cloud Resources in Dynatrace Cloud

C. Installing & Configuring Dynatrace Service Graph Connector on your ServiceNow Instance

D. Run Dynatrace Service Graph Connector Scheduled Data Import Jobs on your ServiceNow Instance

E. Analyze the CMDB Records created\updated by the Dynatrace Service Graph Connector for your Cloud Resources in your ServiceNow Instance

 

 

A. Set up Cloud Resources to be monitored in Dynatrace Cloud

(i) Log into your company's  Dynatrace Cloud  Instance

(ii) Install  Dynatrace OneAgent  on the Cloud Resources to be monitored

 

B. Analyze your Cloud Resources in Dynatrace Cloud

 

Azure Cloud Resources

 

(i)  Navigate to Azure in the Filter Navigator Menu to bring up a list of your current Azure Subscriptions.

(ii) Double click into 1 of your Azure Subscriptions to see it's associated Cloud Resources. We will be analyzing our  az-itxlab1 Azure Subscription. The 1st half of below screenshot shows the Cloud Resources associated with our  az-itxlab1 Azure Subscription.   The Cloud Resources that we will be analyzing are:

• 38 Azure VM's across 2 Regions
• 5 Database Instances
• 15 Storage Accounts
• 4 Load Balancers
• 9 Cloud Functions
• 1 Azure Scale Set

 

The 38 VMs in 2 Regions Tile is selected by default with the 2nd half of the screen displaying the 38 VMs spread across our eastus and westus Azure Regions.

 

 

 

Azure VM's

 

(i) Double click into 1 of the VM Regions displayed   to bring up the list of VM's in that Region. 

 

The below screenshot shows a list of 33 VM's in our  eastus Region. We will be analyzing the  az-itxlab1-east-lin-vic2 Azure VM (shown highlighted in yellow) in this Region. A Target  az-itxlab1-east-lin-vic2   Virtual Machine Instance CI will be created in the CMDB to encapsulate the data associated with this  az-itxlab1-east-lin-vic2 Azure VM.

 

 

 

(ii) Double click into 1 of your Azure VM's to bring up the Host  Screen associated with the Host that the Azure VM is Virtualizing. The below screenshot shows the Host Information associated with the  az-itxlab1-east-lin-vic2   Host  that our sample  az-itxlab1-east-lin-vic2  Azure VM is Virtualizing. A Target  az-itxlab1-east-lin-vic2**  Linux Server  CI will be created in the CMDB to encapsulate the data associated with this  az-itxlab1-east-lin-vic2** Host Entity.

 

 

Make note of the Processes listed in the Host Screen. For our sample  az-itxlab1-east-lin-vic2**   *** Host* we will see these Processes being presented as Application CI's in our Target  az-itxlab1-east-lin-vic2**  Linux *** Server*  CI. You will see them in a  az-itxlab1-east-lin-vic2**  Linux *** Server*  CI screenshot in the CMDB CI Records subsection of the  E. Analyze the CMDB Records created\updated by the Dynatrace Service Graph Connector for your Cloud Resources in your ServiceNow Instance Section further down.

 

(iii) Click on the Properties and tags field on the Host Screen to bring up the Properties and Tabs associated with your Host. The below screenshot shows the Properties and tags associated with our sample  az-itxlab1-east-lin-vic2**   ***Host.*

 

 

Make note of the Tags listed for your Host. For our sample  az-itxlab1-east-lin-vic2    Host we will see these Tags get created as Key Value Records for our Target  az-itxlab1-east-lin-vic2**  Linux Server  CI in the Serial Number Records  subsection of the  E. Analyze the CMDB Records created\updated by the Dynatrace Service Graph Connector for your Cloud Resources in your ServiceNow Instance** Section further down.

 

 

Database Instances

 

(i) Double click into the n Database Components Tile to bring up the list of Database Services that support the n Database Components(Instances) associated with your Subscription. The below screen shot shows the 4 Database Services that support the  5 Database Instances associated with our  az-itxlab1 Azure Subscription.

 

 

The following 5 Database Instances are associated with the above Database Services as shown below:

 

| Database Service | Database Instance |
| Azure Cosmos DB Account (GlobalDocumentDB) | az-itxlab1-cosmodb-global, nonamecosmosdbaccount-b5d8f6a4 |
| Azure Cosmos DB Account (MongoDB) | az-itxlab1-cosmodb |
| Azure SQL Database (DTU) | az-itxlab1-east-sqlserver-1/az-itxlab1-east-sql-db-1 |
| Azure SQL Server | az-itxlab1-east-sqlserver-1 |

 

Storage Accounts

 

(i) Double click into the n  Storage Accounts  Tile\ Azure Storage Service to bring up the list of Azure Storage Accounts associated with your Subscription. The below screen shot shows the list of 15 Storage Accounts associated with our  az-itxlab1 Azure Subscription :

 

 

 

Load Balancers

 

(i) Double click into the n  Load Balancers  Tile to bring up the list of Load Balancers associated with your Subscription. The below screen shot shows the list of 4 Load Balancers  associated with our  az-itxlab1 Azure Subscription :

 

 

Cloud Functions

 

(i) Double click into the n  Cloud Functions  Tile to bring up the list of Cloud Functions  associated with your Subscription. The below screen shot shows the list of 9 Cloud Functions  associated with our  az-itxlab1 Azure Subscription.

 

 

Scale Sets

 

(i) Double click into the n  Scale Sets  Tile to bring up the list of Scale Sets   associated with your Subscription. The below screen shot shows the 1  aks-azitxlab1-12288776-vmss Scale Set associated with our  az-itxlab1 Azure Subscription.

 

 

 

 

AWS Cloud Resources

 

(i)  Navigate to AWS  in the Filter Navigator Menu to bring up a list of your current AWS   Accounts.

(ii) Double click into 1 of your AWS Accounts  to see it's associated Cloud Resources. We will be analyzing our  monitor 698091055457   AWS Account.

 

The 1st half of the below screenshot shows the Cloud Resources associated with our  monitor 698091055457   AWS Account   .   The Cloud Resources that we will be analyzing are:

 

• 98 AWS EC2 Instances across 4 Availability Zones
• 2 Amazon RDS Components
• 3 Amazon DynamoDB Tables
• 25 Amazon S3 Buckets
• 15 Load Balancers
• 5 Lambda Functions
• 6 Auto Scaling Groups

 

The EC2  Tile is selected by default with the 2nd half of the screen displaying the 98 EC2 Instances  spread across our us-east-2a,    us-east-2c, us-west-2a  and us-west-2b  Availability Zones.

 

 

 

AWS EC Instances

 

(i) Double click into 1 of the Availability Zones displayed   to bring up the list of VM's in that Availability Zone. 

 

The below screenshot shows a list of 92 EC2 Instances in our  us-east-2a  Availability Zone. We will be analyzing the  DFOUND_Eng_org2_east2_vpc1_win_tomcat EC2 Instance (shown highlighted in yellow) in this Availability Zone that Virtualizes a  ec2amaz-0ujoniv Windows Server.   A Target  DFOUND_Eng_org2_east2_vpc1_win_tomcat   Virtual Machine Instance CI will be created in the CMDB to encapsulate the data associated with this  DFOUND_Eng_org2_east2_vpc1_win_tomcat   AWS EC2 Instance.

 

 

(ii) Double click into 1 of your EC2 Instance's to bring up the Host  Screen associated with the Host that the EC2 Instance is Virtualizing. The below screenshot shows the Host Information associated with the  ec2amaz-0ujoniv ** Host  that our sample  DFOUND_Eng_org2_east2_vpc1_win_tomcat EC2 Instance is Virtualizing. A Target  ec2amaz-0ujoniv Windows Server  CI will be created in the CMDB to encapsulate the data associated with this  ec2amaz-0ujoniv** Host Entity.

 

 

Make note of the Processes listed in the Host Screen. For our sample  ec2amaz-0ujoniv Host we will see these Processes being presented as Application CI's in our Target  ec2amaz-0ujoniv Windows Server  CI. You will see them in a  ec2amaz-0ujoniv Windows Server  CI screenshot in the CMDB CI Records subsection of the  E. Analyze the CMDB Records created\updated by the Dynatrace Service Graph Connector for your Cloud Resources in your ServiceNow Instance Section further down.

 

(iii) Click on the Properties and tags field on the Host Screen to bring up the Properties and Tabs associated with your Host. The below screenshot shows the Properties and tags associated with our sample  ec2amaz-0ujoniv Host. 

 

 

Make note of the Tags listed for your Host. For our sample  ec2amaz-0ujoniv Host we will see these Tags get created as Key Value Records for our Target  ec2amaz-0ujoniv Windows Server  CI in the Serial Number Records  subsection of the  E. Analyze the CMDB Records created\updated by the Dynatrace Service Graph Connector for your Cloud Resources in your ServiceNow Instance Section further down.

 

Amazon RDS Components

 

(i) Double click into the n  RDS Instances  Tile\ Amazon RDS Service to bring up the list of RDS Instances  associated with your AWS Account. The below screen shot shows the list of 2 RDS Instances  associated with our  monitor 698091055457   AWS Account.

 

 

 

Amazon DynamoDB Tables

 

(i) Double click into the n  DynamoDB  Tile\ Amazon DynamoDB  Service to bring up the list of DynamoDB Tables  associated with your AWS Account. The below screen shot shows the list of 3 DynamoDB Tables  associated with our  monitor 698091055457   AWS Account.

 

 

 

Amazon S3 Buckets

 

(i) Double click into the n  Cloud Services  Tile\ Amazon S3  Service to bring up the list of S3 Buckets  associated with your AWS Account. The below screen shot shows the list of 25 S3 Buckets  associated with our  monitor 698091055457   AWS Account.

 

 

 

Load Balancers

 

(i) Double click into the n  Load Balancers  Tile to bring up the list of Load Balancers  associated with your AWS Account. The below screen shot shows the  15 Load Balancers - (2 Classic Loaders, 9 Application  Load Balancers and 4 Network Load Balancers) associated with our  monitor 698091055457   AWS Account with the 9   Application Load Balancers Tab being open showing the 1st 4 of these Load Balancers.

 

 

 

Lambda Functions

 

(i) Double click into the n  Lamba Functions Tile\ AWS Lamba Service  to bring up the list of Lamba Functions  associated with your AWS Account. The below screen shot shows the  5 Lamba Functions associated with our  monitor 698091055457   AWS Account.

 

 

 

Auto Scaling Groups

 

(i) Double click into the n  Auto Scaling Groups  Tile to bring up the list of Auto Scaling Groups  associated with your AWS Account. The below screen shot shows the 6 Auto Scaling Groups associated with our  monitor 698091055457   AWS Account.

 

 

 

 

Kubernetes Cloud Resources

 

(i)  Navigate to Kubernetes  in the Filter Navigator Menu to bring up the Overview of Kubernetes clusters Screen showing a current list of your  Kubernetes Clusters. The below screenshot shows our single  otel-demo-on-k3s   Kubernetes Cluster with it's associated Cloud Resources. We will be analyzing this  otel-demo-on-k3s   Kubernetes Cluster.

 

 

We will be analyzing the following types of Cloud Resources for our   otel-demo-on-k3s   Kubernetes Cluster :

 

• Namespaces
• Kubernetes Services
• Pods
• Docker Containers
• Nodes

 

Namespaces

 

(ii) Double click on the n Namespaces Link to the right of 1 of your Clusters on the  Overview of Kubernetes clusters Screen to bring up the Kubernetes namespaces screen for that  Cluster. The below screenshot shows the 7 Namespaces associated with our  otel-demo-on-k3s   Kubernetes Cluster. 

 

 

 

Kubernetes Services

 

(iii) Double click on the n Kubernetes Services  Link to the right of 1 of your Clusters  on the Overview of Kubernetes clusters Screen to bring up the Kubernetes Services  screen for your Cluster. The below screenshot shows that there are 34 Kubernetes Services  associated with our  otel-demo-on-k3s   Kubernetes Cluster   with the 1st 8 of these being shown below.

 

 

 

Pods

 

(iv) Double click on   icon to the far right of 1 of your Clusters  on the  Overview of Kubernetes clusters Screen to bring up the below Menu for that Cluster:

 

 

(v) Double click on the Pods list Menu option to bring up the Kubernetes Pods Screen for your Cluster. The below screenshot shows that there are 50 Kubernetes Pods  associated with our  otel-demo-on-k3s   Kubernetes Cluster  with the 1st 8 of these being shown below. 

 

We will be analyzing the accounting-58c9b7d6b5-wtdx7 Pod  in our  otel-demo-on-k3s   Kubernetes Cluster (shown highlighted in yellow in the below screenshot) that Contains a  accounting-58c9b7d6b5-wtdx7 accounting Container and Runs on a  ip-10-2-0-55.us-east-2.compute.internal Node which in turn is Hosted on a  ip-10-2-0-55.us-east-2.compute.internal Host Machine.

 

 

Docker Containers

 

(vi) Double click on 1 of the Pods on your  Kubernetes Pods Screen to bring up the Overview of the Pod Screen for that Pod. A list of Containers and Processes associated with that Pod will be displayed on this Screen.

 

The below screenshot shows the  Overview of the Pod Screen for our sample  accounting-58c9b7d6b5-wtdx7 Pod with an  accounting-58c9b7d6b5-wtdx7** accounting   Container and  Accounting.dll accounting-* (accounting-58c9b7d6b5-wtdx7) Process** being displayed on the Screen.

 

 

(vii) Double click on 1 of the Containers displayed on this Screen to being up the Overview of Container Screen for that Container.

 

The below screenshot shows the  Overview of Container Screen for the  accounting-58c9b7d6b5-wtdx7** accounting   Container associated with our sample  accounting-58c9b7d6b5-wtdx7 **** Pod with the Process analysis** section of the Screen being displayed.

 

It shows the same Accounting.dll accounting-* (accounting-58c9b7d6b5-wtdx7) Process that was displayed on the above  accounting-58c9b7d6b5-wtdx7 Pod Overview Screen.

 

 

(viii) Click on the Properties and tags field on the Overview of the Container  Screen to bring up the Properties and Tags  Screen associated with your Container.

 

 

Make note of the Container image name displayed for your Container. For the  accounting-58c9b7d6b5-wtdx7** accounting   Container associated with our sample  accounting-58c9b7d6b5-wtdx7 **** Pod we can see that a  ghcr.io/open-telemetry/demo:2.2.0-accounting   Container Image is associated with the Container** (circled in blue in the above screenshot)

 

An accompanying  ghcr.io/open-telemetry/demo:2.2.0-accounting Docker Image CI will be created in the CMDB for this  accounting-58c9b7d6b5-wtdx7** accounting   Container**.

 

 

Nodes

 

(ix) Double click into 1 of your Kubernetes Clusters  on the Overview of Kubernetes clusters Screen to bring up the Overview of Kubernetes Cluster  Screen for that Cluster. The  Node analysis section of the screen listing the Nodes in your Cluster is displayed by default.

 

The below screenshot shows the  Overview of Kubernetes cluster  Screen for our  otel-demo-on-k3s   Kubernetes Cluster with the 2 Nodes associated with our  otel-demo-on-k3s   Kubernetes Cluster being listed. The  ip-10-2-0-55.us-east-2.compute.internal Node that our sample  accounting-58c9b7d6b5-wtdx7 Pod Runs on is shown on this Screen (highlighted in yellow).

 

 

 

(x) Double click on 1 of the Nodes on this Screen to bring up the Overview of the Node Screen for that Node. The below screenshot shows the Overview of the Node Screen for our  ip-10-2-0-55.us-east-2.compute.internal Node.

 

Notice the Host field on this Screen. The below screenshot shows that our  ip-10-2-0-55.us-east-2.compute.internal Node is hosted on our  ip-10-2-0-55.us-east-2.compute.internal Host Machine which will have a Target ip-10-2-0-55 ** Linux Server CI** created for it in the CMDB.

 

 

 

 

C. Installing & Configuring Dynatrace Service Graph Connector on your ServiceNow Instance

 

(i) Login to your ServiceNow Instance

(ii) Install the following Applications & Plugins in the order shown:

 

Applications

 

1. Integrations Commons for CMDB: sn_cmdb_int_util
2. CMDB CI Class Model: sn_cmdb_ci_class
3. ITOM Discovery License: com.snc.itom.discovery.license (Included with full Discovery Product)
4. Event Management: sn_em_ai (for enabling the capturing of events from Dynatrace)  
5. Service Graph Connector for Observability - Dynatrace: sn_dynatrace_integ

 

Plugins

 

6 .  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 the  SGC Central  Tab in the  CMDB Workspace

(iv) Go through all  SGC Central  Steps for creating a New  Dynatrace Classic Connection  and associated  Scheduled Imports  as outlined in the ServiceNow Documentation: Configure Service Graph Connector for Observability - Dynatrace using SGC Central 

 

Create and Test Connection  step

 

(i) Navigate to the  Create and Test Connection  step listed in the Left Hand Navigator of  Setup  to bring up the below screen:

 

 

 

Connection name: Provide a  Name  that will allow you to easily identity the  Dynatrace Tenant  that you are connecting to, e.g. USA. 

 

Hostname: This Name will be used as part of the naming convention for the newly created  Customer Specific Data Sources & Import Sets  as per below.

 

| Customer Specific Data Sources | Data Source Name - Connection Name |
| Customer Specific Scheduled Import Jobs | Import Job Name - Connection Name |

 

API Key: Enter " api-token API Key" where _ API Key _ is replaced with the  API Key  associated with the  Customer specific Dynatrace Tenant  that you are connecting to.

 

(ii) Click on the  Continue  Pushbutton

 

• A new  Child   Connection & Credential Alias  Record is created with the  Credential Details  specified. This  Child   Connection & Credential Alias  Record is associated with the OOTB Parent  Dynatrace Connection Connection & Credential Alias  Record as shown in the below screen shot. We specified  USA  for our example so  USA  is shown as the  Child Connection & Credential Alias  below.

 

 

 

• A new set of  Customer specific Data Sources and Scheduled Imports  are created that contain the  Connection Name  specified in the  Create and test Connection  Screen. An example of the  Customer specific Data Sources and Scheduled Imports  that get created is shown below, where  USA  was used to identify our Customer specific Schedule Imports and Data Sources:

 

 

• A Service Graph Connection[sn_cmdb_int_util_service_graph_connection] Record is created that encapsulates the  Properties ,  Data Sources  and  Scheduled Data Import  Jobs associated with the newly created  Child Alias Connection & Credential  Record. The screenshot below shows the Service Graph Connection[sn_cmdb_int_util_service_graph_connection] Record that was created for our  USA   Child Alias Connection & Credential  Record:

 

 

Note: The tags Property is used to Filter what Entities get ingested from Dynatrace into the CMDB where you Tag the Dynatrace Entities that you want to ingest in the Dynatrace Backend side and then specify that Tag in the tags property listed above.

 

Configure Import Schedule  step

 

Dynatrace Service Graph Connector  Scheduled Import Jobs will be run at the interval you specify to ingest data from the  Dynatrace Tenant  that the  Dynatrace**  Service Graph Connector** connects to. The CMDB database on your ServiceNow Instance will be populated with this ingested data.

 

The  Dynatrace**  Service Graph Connector  comes with  37  Out of the Box  Data Source  and  Scheduled Data Import  Templates. These Templates were used for creating your own  Customer Specific Data Sources  and  Scheduled Data Imports  in the previous  Create and Test Connection** step. Please refer to this ServiceNow Data mapping for Service Graph Connector for Observability - Dynatrace Documentation page for more details on these Schedule Import Jobs.

 

(i) Navigate to the  Configure import Schedule  step listed in the Left Hand Navigator of  Setup  to bring up the below screen:

 

 

(ii) Turn on the Parent  SGO-Dynatrace Hosts - Connection Name  Scheduled Import job by changing it's  Active  Field from  false  to  true,  in our case the  SGO-Dynatrace Hosts - USA  Scheduled Import job.

(iii) The  SGO-Dynatrace Hosts  job is set to run  Daily  by default. Specify at what  Repeat Intervals  that you want this Job to run. 

 

D. Run Dynatrace Service Graph Connector Scheduled Data Import Jobs on your ServiceNow Instance

 

(i) Navigate to  Scheduled Data Imports  under  Dynatrace Observability  in the Filter Menu. 37 Scheduled Import Jobs should be listed containing the  Connection Name  that you specified in the  Create and Test Connection  step in the previous  C. Installing & Configuring Dynatrace Service Graph Connector on your ServiceNow Instance  Section. The below screenshot shows our 37  USA  Scheduled Import Jobs:

 

 

(ii) Open the  SGO-Dynatrace Hosts - Connection Name  Parent Scheduled job record, in our case the  SGO-Dynatrace Hosts _- _USA  Parent Scheduled job record, and click on the  Execute  button

(iii) Navigate to  Concurrent Import Sets  in the Filter Menu.

• Wait for all 37 Scheduled Data Import jobs to finish

 

For each  Scheduled Data Import  Job, the following happens:

 

1. Payload Records  are created in the appropriate  Scheduled Import Staging Table  with data that is loaded from the  Scheduled Import Data Source.
2. These  Payload Records  are then passed to the  Robust Import Set Transformer  associated with the  Scheduled 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) ).
3. Output Records  from the  Robust Import Set Transformer  are then sent to the Identification & Reconciliation(IRE) Engine for processing.

4. The* Identification & Reconcilation(IRE) Engine does the following with each  **Output Record* :

5. It  Creates\Updates  the appropriate CI Record in the CMDB 

6. 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  Dynatrace**  Event Processing* (_described further down in the G. Event Management* Section below_).

 

E. Analyze the CMDB Records created\updated by the Dynatrace Service Graph Connector for your Cloud Resources in your ServiceNow Instance

 

There are 4 types of Records created by the Dynatrace Service Graph Connector in the CMDB:

 

• CMDB CI[cmdb_ci] Records
• Software Installation[cmdb_sam_sw_install] Records - If Software Asset Management(SAM) enabled
• Software Instance[cmdb_software_instance] + Software Package[cmdb_ci_spkg] Records - If Software Asset Management(SAM) not enabled
• Serial Number[cmdb_serial_number] Records
• Key Value[cmdb_key_value] Records

 

 

CMDB CI Records

 

(i)    Navigate to  cmdb_ci.list  in the Filter Menu

(ii)   Group by  Discovery Source

(iii)  Navigate to the  SGO-Dynatrace  Discovery Source and double click on its Discovery source:SGO-Dynatrace(n) link where  n  represents the Number of CMDB records(entities) Created\Updated by the Dynatrace Service Graph Connector.

 

--> All CMDB CI Records that were created\updated by the  Dynatrace Service Graph Connector  are listed. 

 

(iv) Group By  Class

 

A List of CMDB CI Records Created\Updated by the Dynatrace Service Graph Connector will be displayed grouped by Class. 

 

Azure & AWS CI's

 

The screen shot below shows the list of SGO-Dynatrace CI's that were brought in by the Dynatrace Service Graph Connector with the  az-itxlab1 Cloud Service Account CI that was created for our  az-itxlab1 Azure Subscription and the  monitor 698091055457 Cloud Service Account CI that was created for our  monitor 698091055457 AWS Cloud Service Account being highlighted.

 

• The  az-itxlab1 Cloud Service Account CI that was created for our  az-itxlab1 Azure Subscription and the  monitor 698091055457 Cloud Service Account CI that was created for our  monitor 698091055457 AWS Cloud Service Account  is highlighted under the Cloud Service Account CIs.

 

• The  az-itxlab1-east-lin-vic2 Virtual Machine Instance CI and associated   az-itxlab1-east-lin-vic2 Linux Server CI that was created for our  az-itxlab1 Azure Subscription  is highlighted under the Virtual Machine Instance and Linux Server CI's respectively

 

• The  DFOUND_Eng_org2_east2_vpc1_win_tomcat Virtual Machine Instance CI and associated ec2amaz-0ujoniv Windows Server CI that was created for our  monitor 698091055457 AWS Cloud Service Account is highlighted under the Virtual Machine Instance and Windows Server CI's respectively.

 

 

az-itxlab1-east-lin-vic2 Linux Server CI

 

The screen shot below shows all the  Linux Server Summary fields that were populated by the Dynatrace Service Graph Connector  for the az-itxlab1-east-lin-vic2  Linux Server CI.

 

 

Related Items

 

The below screenshot shows the 2 different Runs on::Runs (child) - Applications and Virtualized by::Virtualizes (parent) - Virtual Machine Instances  CI Relationship Types with the associated Related Item CI's  being listed under these 2 Relationship Types.

 

 

• The  Application CI's  shown under the Runs on::Runs (child) - Applications Relationship Type are listed as Processes for the  az-itxlab1-east-lin-vic2 Host in the  az-itxlab1-east-lin-vic2 Host Entity Screen Shot in the in the Azure Cloud Resources - Azure VM's**   sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud** Section.

 

• The  az-itxlab1-east-lin-vic2 Virtual Machine Instance CI shown under the Virtualized by::Virtualizes (parent) - Virtual Machine Instances Relationship Type is shown highlighted in the Virtual Machine Instance  CI's screenshot under the above  CMDB CI Records  heading.

 

Related Lists

 

The below screenshot shows all the Related Lists , associated with the  az-itxlab1-east-lin-vic2 Linux Server CI , being displayed in the Tabbed area at the bottom of the  az-itxlab1-east-lin-vic2 Linux Server CI Form. It shows the Software Installations, S** erial Numbers  and Key Values Related Lists being populated with data ingested by the Dynatrace Service Graph Connector**.

 

The  Software Installations  Related List is shown being populated with a single Ubuntu Operating System   Software Installation Record (The Dynatrace Service Graph Connector only creates Operating System Software Installation Records in the Software Install Table).

 

 

 

ec2amaz-0ujoniv  Windows Server CI

 

The screen shot below shows all the Windows Server Summary fields that were populated by the Dynatrace Service Graph Connector  for the  ec2amaz-0ujoniv**  **Windows Server CI.

 

 

Note: The associated  ec2f6caf-52d4-9339-a30c-0ad9533a874   cmdb_serial_number Record is shown in an Embedded Section of the  ec2amaz-0ujoniv**  Windows *** Server CI* Form as oppose to in a Serial Number Related List Tab like it was for the previous  az-itxlab1-east-lin-vic2  Linux Server CI.

 

Related Items

 

The below screenshot shows the 2 different Runs on::Runs (child) - Applications and Virtualized by::Virtualizes (parent) - Virtual Machine Instances  CI Relationship Types with the associated Related Item CI's  being listed under these 2 Relationship Types.

 

 

• The  Application CI's  shown under the Runs on::Runs (child) - Applications Relationship Type are listed as Processes for the Host in the  ec2amaz-0ujoniv**   Host Entity Screen Shot in the in the AWS Cloud Resources - EC2 Instances *** * sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud Section.

 

• The  DFOUND_Eng_org2_east2_vpc1_win_tomcat Virtual Machine Instance CI shown under the Virtualized by::Virtualizes (parent) - Virtual Machine Instances Relationship Type is shown highlighted in the Virtual Machine Instance  CI's screenshot under the above  CMDB CI Records  heading.

 

Related Lists

 

The below screenshot shows all the Related Lists , associated with the  ec2amaz-0ujoniv Windows Server CI , being displayed in the Tabbed area at the bottom of the  ec2amaz-0ujoniv Windows Server CI     Form. It shows the Software Installations and Key Values  Related Lists being populated with data ingested by the Dynatrace Service Graph Connector.

 

The  Software Installations  Related List is shown being populated with a single  Windows Server Operating System   Software Installation Record (The Dynatrace Service Graph Connector only creates Operating System Software Installation Records in the Software Install Table).

 

 

 

Cloud Database CI's

 

The below screen shot shows 8  Cloud Database  CI's that were ingested from a combination of Dynatrace Azure Database Instance and AWS RDS Instance Entities. 

 

The Azure Database Instances associated with our  az-itxlab1 Azure Subscription , that were listed in the  Azure Cloud Resources - Database Instances sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud Section, are shown in the below screen shot circled in blue.

 

The  2 RDS Instances  associated with our  monitor 698091055457   AWS Account , that were listed in the AWS Cloud Resource - AWS RDS Components  sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud Section, are shown in the below screen shot circled in orange.

 

 

 

Cloud Storage Account CI's

 

The below screen shot shows 29 Cloud Storage Account CI's that were ingested from Dynatrace where each Cloud Storage Account CI represents an Azure Storage Account Entity in Dynatrace. You will notice that the Cloud Storage Account CI's circled in Blue are associated with our  az-itxlab1 Azure Subscription as per their listing in the  Azure Cloud Resources - Storage ** Account  sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud** Section.

 

 

 

Load Balancer CI's

 

The below screen shot shows 40  Load Balancer  CI's that were ingested from a combination of Dynatrace Azure and AWS Load Balancer  Entities. 

 

You will notice that 2 of the Azure Load Balancers  associated with our  az-itxlab1 Azure Subscription , that were listed in the  Azure Cloud Resources - Load Balancer  sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud Section, are shown in the below screen shot circled in blue.

 

You will notice that 2 of the AWS Load Balancers  associated with our  monitor 698091055457   AWS Account , that were listed in the AWS Cloud Resource - Load Balancers  sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud Section, are shown in the below screen shot circled in orange.

 

 

 

Cloud Function CI's

 

The below screen shot shows 87  Cloud Function  CI's that were ingested from a combination of Dynatrace Azure Cloud Function  and AWS Lamba Function  Entities. 

 

You will notice that 1 of the Azure Cloud Functions  associated with our  az-itxlab1 Azure Subscription , that was listed in the  Azure Cloud Resources - Cloud Function  sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud Section, is shown in the below screen shot circled in blue.

 

You will notice that 1 of the AWS Lamba Functions associated with our  monitor 698091055457   AWS Account , that was listed in the AWS Cloud Resources - Lamba Functions  sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud Section, is shown in the below screen shot circled in orange.

 

 

 

Scale Sets CI's

 

The below screen shot shows 4  Instance Scale Set  CI's that were ingested from Dynatrace where each Instance Scale Set  CI represents an Azure Scale Set  Entity in Dynatrace. You will notice that the Instance Scale Set  CI circled in Blue is associated with our  az-itxlab1 Azure Subscription as per it's listing in the  Azure Cloud Resources - Storage ** Account  sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud** Section.

 

 

 

 

DynamoDB Table CI's

 

The below screen shot shows 9  DynamoDB Table  CI's that were ingested from Dynatrace where each DynamoDB Table  CI represents an  AWS DynamoDB Table  Entity in Dynatrace. You will notice that the DynamoDB Table  CI's circled in Blue are associated with our  monitor 698091055457   AWS Account  as per their listing in the AWS Cloud Resources - DynamoDB Table**   sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud** Section.

 

 

 

Cloud Object Storage CI's

 

The below screen shot shows 25  Cloud Object Storage  CI's that were ingested from Dynatrace where each Cloud Object Storage  CI represents an  AWS S3 Bucket  Entity in Dynatrace. You will notice that the S3 Bucket  CI's circled in Blue are associated with our  monitor 698091055457   AWS Account  as per their listing in the AWS Cloud Resources - S3 Bucket**   sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud** Section.

 

 

 

Cloud Resource CI's

 

The below screen shot shows 6  Cloud Resource  CI's that were ingested from Dynatrace where each Cloud Resource  CI represents an AWS  Autoscaling Group  Entity in Dynatrace. All of the below Cloud Resource CI's are associated with our  monitor 698091055457   AWS Account  as per their listing in the AWS Cloud Resources - Autoscaling Group**   sub section of the B. Analyze your Cloud Resources in Dynatrace Cloud** Section.

 

 

 

 

 

Kubernetes CI's

 

The screen shot below shows the list of SGO-Dynatrace Kubernetes CI's that were brought in by the Dynatrace Service Graph Connector with the  otel-demo-on-k3s   Kubernetes Cluster CI and our sample  accounting-58c9b7d6b5-wtdx7 Pod  and the  ip-10-2-0-55.us-east-2.compute.internal Node that it runs on being highlighted. 

 

 

otel-demo-on-k3s Kubernetes Cluster CI

 

The screen shot below shows the  otel-demo-on-k3s Kubernetes Cluster CI Screen with the Cluster of::Cluster (parent) - Kubernetes Nodes, Contained::Contained by (parent) - Kubernetes Pods, Contained::Contained by (parent) - Kubernetes Services CI Relationship Types, **and their associated  Related Item CI's  being listed under these  Relationship Types , being displayed.** 

 

 

• The Kubernetes Nodes**   ***CI's*  shown under the Cluster of::Cluster (parent) - Kubernetes Nodes Relationship Type are listed as Nodes  for the Cluster in the Kubernetes Cloud Resources - Nodes sub section of the  B. Analyze your Cloud Resources in Dynatrace Cloud Section with the  ip-10-2-0-55.us-east-2.compute.internal Node that our sample  accounting-58c9b7d6b5-wtdx7 Pod   Runs on being circled in blue. 

 

• The Kubernetes Pods**   ***CI's*  shown under the Contained by::Contains (parent) - Kubernetes Pod Relationship Type are listed as Pods  for the Cluster in the Kubernetes Cloud Resources - Pods  sub section of the  B. Analyze your Cloud Resources in Dynatrace Cloud Section with our sample  accounting-58c9b7d6b5-wtdx7 Pod  being circled in blue.  .

 

• The Kubernetes Services**   ***CI's*  shown under the Contained by::Contains (parent) - Kubernetes Services Relationship Type are listed as Kubernetes   Services  for the Cluster in the Kubernetes Cloud Resources - Kubernetes Services  sub section of the  B. Analyze your Cloud Resources in Dynatrace Cloud Section.

 

• The Kubernetes Namespaces**   ***CI's*  shown under the Contained by::Contains (parent) - Kubernetes Namespaces Relationship Type are listed as Kubernetes Namespaces  for the Cluster in the Kubernetes Cloud Resources - Kubernetes Namespaces  sub section of the  B. Analyze your Cloud Resources in Dynatrace Cloud Section.

 

 

accounting-58c9b7d6b5-wtdx7 Pod CI

 

The screen shot below shows the accounting-58c9b7d6b5-wtdx7 Pod CI Summary Screen along with the Contained::Contained by (child) - Kubernetes Clusters, Contained::Contained by (parent) - Docker Containers, Runs on::Runs(parent) - Kubernetes Nodes  CI Relationship Types, and their associated  Related Item CI's  being listed under these  Relationship Types , being displayed .  

 

A single Kubernetes Pod Key Value Record, that can be found in the Key Values[cmdb_key_value] Table, is also displayed.

 

 

 

 

• Our  otel-demo-on-k3s Kubernetes Cluster CI is shown under the Contained::Contained by (child) - Kubernetes Clusters Relationship Type
• The  accounting-58c9b7d6b5-wtdx7** accounting   Docker Container CI that it Contains is shown under the  Contained::Contained by (parent) - Docker Containers , Runs on::Runs(parent) **Relationship Type
• The  10-2-0-55.us-east-2.compute.internal Node that it Runs on is shown under the Runs on::Runs(parent) - Kubernetes Nodes Relationship Type

 

The below screenshot shows the Dependency Diagram for this  accounting-58c9b7d6b5-wtdx7 Pod CI where it is shown Containing the  accounting-58c9b7d6b5-wtdx7** accounting   Docker Container and Running on the  10-2-0-55.us-east-2.compute.internal Node which in turn is shown Running on the  10-2-0-55 Linux Server which in turn is Virtualized by a  DFOUND_Eng_org2_east2_vpc1_otel_demo_node2 **** Virtual Machine** (An AWS EC2 Instance Entityin Dynatrace)

 

 

 

accounting-58c9b7d6b5-wtdx7accounting Docker Container CI

 

The screen shot below shows the  accounting-58c9b7d6b5-wtdx7accounting Docker Container CI  Summary Screen along with the Contained::Contained by (child) - Kubernetes Pods, Instantiates::Instantiated by (child) - Docker Images, Runs on::Runs(child) - Applications,Runs on::Runs(parent) - Linux Servers  CI Relationship Types, and their associated  Related Item CI's  being listed under these  Relationship Types , being displayed .  

 

 

 

• Our  accounting-58c9b7d6b5-wtdx7 Pod  CI is shown under the Contained::Contained by (child) - Kubernetes Pods Relationship Type
• The  ghcr.io/open-telemetry/demo:2.2.0-accounting Docker Image CI that instantiated this  accounting-58c9b7d6b5-wtdx7accounting Docker Container is shown under the Instantiates::Instantiated by (child) - Docker Images Relationship Type
• The Accounting.dll accounting-* (accounting-58c9b7d6b5-wtdx7) Application CI is shown as a Running Process for the Container in the Kubernetes Cloud Resources - Containers  sub section of the  B. Analyze your Cloud Resources in Dynatrace Cloud Section.
• The ip-10-2-0-55 Linux Server CI is shown as the Host Machine that Hosts the Container  in the Kubernetes Cloud Resources - Containers  sub section of the  B. Analyze your Cloud Resources in Dynatrace Cloud Section.

 

 

Software Installation Records

 

Software Asset Management(SAM) enabled

 

For ServiceNow Instances that have Software Asset Management(SAM) enabled, the Software Install Records associated with Created\Updated Computer CI's will be ingested into the Software Installations[cmdb_sam_sw_install] Table.

 

Software Asset Management(SAM) not enabled

 

For ServiceNow Instances that do not have Software Asset Management(SAM) enabled, the Software Install Records associated with Created\Updated Computer CI's will be ingested into the Software Instances[cmdb_software_instance] Table along with associated Software Package Records being ingested into the Software Packages[cmdb_ci_spkg] Table.

 

Note: All that is needed to enable Software Asset Management is the free SAM Foundation plugin. Installing this plugin triggers the Software Install Records being populated into the Software Installations[cmdb_sam_sw_install] Table. Installing this free SAM Foundation plugin is a recommended Best Practice for customers that believe that they may be using Software Asset Management Professional (SAM Pro) in the future. These customers would then not have to migrate Software Records from the Software Instances[cmdb_software_instance] Table to the Software Installations[cmdb_sam_sw_install] Table at the point in time that they would be installing Software Asset Management Professional (SAM Pro).

 

The Use Case outlined in this Article is for a ServiceNow Instance with Software Asset Management(SAM) enabled, so to see the Software Install Records associated with Computer CI's that were Created\Updated by the Dynatrace Service Graph Connector, the steps below direct you to navigate to the Software Installations[cmdb_sam_sw_install] Table:

 

(i) Navigate to cmdb_sam_sw_install.list in the Filter Menu

(ii) Group by Discovery Source

(iii) Navigate to the SGO-Dynatrace Discovery Source and double click on its Discovery source:SG-SCCM (n) link where n represents the Number of Software Install Records Created\Updated by the Dynatrace Service Graph Connector.

(iv) A List of Software Install Records Created\Updated by the Dynatrace Service Graph Connector will be displayed. The screen shot below shows the Operating Software Install Records displayed in this List for all our AWS and Azure Devices in our Dynatrace Backend. Our sample Azure  az-itxlab1-east-lin-vic2  Linux Server is shown highlighted in this Screenshot.

 

 

Note: Only Software Install Records for the Operating System running on Devices ingested from Dynatrace are created in the Software Install Table.

 

Serial Number Records

 

(i) Navigate to cmdb_serial_number.list in the Filter Menu

(ii) A List of all the Serial Number Records in your ServiceNow Instance will be displayed like the one shown in the screen shot below:

 

 

(iii) To see the  Serial Number  Records associated with any of your Devices from Dynatrace Backend, type it's name into the  Configuration Item  Search Field in this list. The screen shot below shows the  Serial Number  Records associated with our  az-itxlab1-east-lin-vic2 Linux Server CI and  ec2amaz-0ujoniv Windows Server CI respectively.

 

 

Key Value Records

 

(i)  Navigate to  cmdb_key_value.list  in the Filter Menu

(ii) To see the Key Value  Records associated with any of your Devices from Dynatrace Backend, type it's name into the  Configuration Item  Search Field in this list.

 

The screen shot below shows the Key Value  Records associated with our  ec2amaz-0ujoniv Windows Server CI  

 

 

The screen shot below shows the Key Value  Records associated with our  az-itxlab1-east-lin-vic2

 Linux Server CI