logo

NJP

Introduction to Service Graph Connector for Observability Dynatrace

Import · Sep 14, 2021 · article

Event Management

During the guided setup of the Service Graph Connector for Observability Dynatrace there is a step to Create Default Notification Payload Template. This step has a button called Problem Notification Setup that when clicked will execute multiple API calls to Dynatrace to setup event ingestion. During this process the DynatraceAPI user will have a new secure password generated for it that Dynatrace will use to connect back to the ServiceNow instance.

This will create the following in the Dynatrace environment:

image

image

A user can modify these records in the Dynatrace application if they need further fine tuning.

Notifications will then be sent from Dynatrace to the EM-Connector Inbound Event API. This API will pass the information to the Push Connector (sn_em_connector_listener) defined by this integration to parse the notification and create an event if there is a corresponding CI in the CMDB. From there, standard event management deduplication and alert creation are followed.

Once an alert is created, the Alert Management Rule is executed. This will call the associated subflows for further processing of the alert.

Metric Ingestion

Just in time metric collection is possible if the ServiceNow instance has MetricBase installed and configured.

Once an alert comes in that is associated to a computer CI, the SGO-Dynatrace Alert Subflow is kicked off that will then query the sn_dynatrace_integ_event_mapping table and the Dynatrace API for that CI and determine if any metrics are associated to that alert and CI. The metric will then fetch data in minute increments for the hour prior to the alert and save it in the sn_observability_metrics table.

Log Ingestion

Just in time log collection is possible. This requires the alert is bound to a computer CI and that Dynatrace is storing logs off that CI.

Once an alert comes in that is associated to a computer CI, the SGO-Dynatrace Alert Subflow is kicked off that will query the Dynatrace API to determine if logs are stored on that CI. It will then iterate through each stored log and return the last 10k log messages and save them to the alert as an attachment.

ATF Tests

The Service Graph Connector for Observability Dynatrace integration ships with a set of OOTB ATF Tests. These can be run by running the test suite SGO-Dynatrace Integration Tests. These tests will put example records into the import set tables, running the transformer, and verifying the output. These tests can be helpful in debugging issues and verifying the environment is set up correctly in order to process the data.

Demo Data

If the admin selects Load Demo Data during installation, then demo data records will be put into the CMDB. These records may be found by navigating to the cmdb_ci table and filtering by discovery_source = SGO-Dynatrace. These records may be helpful to see the output of the integration without setting up the connection. Service Maps may need to be recomputed in order to view the service map after loading the demo data.

Labels:

View original source

https://www.servicenow.com/community/cmdb-blog/introduction-to-service-graph-connector-for-observability/ba-p/2275131