Dynatrace

this guide explains how to connect resolve ai with dynatrace resolve uses this connection to ingest metrics, logs, dashboards, and problems for incident investigations 1\ create tokens dynatrace exposes two api surfaces — the classic environment api and the newer platform (grail) api resolve needs a token for each access token (classic environment api) in dynatrace, open apps → access tokens click generate new token name it resolve access token select the following scopes metrics read entities read problems read events read settings read click generate token and copy the value platform token (grail / documents api) in dynatrace, open account management → identity & access management → platform tokens click generate new token name it resolve platform token select the following scopes storage\ buckets\ read storage\ bucket definitions\ read storage\ logs\ read storage\ metrics\ read storage\ spans\ read storage\ events\ read storage\ entities\ read storage\ smartscape\ read storage\ system\ read document\ documents\ read click generate token and copy the value security best practice never store credentials in plaintext in configuration files or source control treat both tokens as secrets and rotate them on a regular cadence 2\ find your environment urls resolve needs the base url for each dynatrace api surface both can be found in your dynatrace tenant url classic api url ( apiurl ) https //\<tenant id> live dynatrace com platform api url ( appurl ) https //\<tenant id> apps dynatrace com where \<tenant id> is the alphanumeric identifier for your environment (e g abc12345 ) 3\ connect dynatrace set up the integration either in the resolve ui or in the satellite configuration connect via resolve ui open dynatrace integration https //app0 resolve ai/integrations/dynatrace/connect in resolve click add connection enter a name (ex dynatrace main ) set the environment that matches the data this connection will ingest (ex production ) paste the access token from step 1 (access token) paste the platform token from step 1 (platform token) enter your api url (ex https //abc12345 live dynatrace com ) enter your app url (ex https //abc12345 apps dynatrace com ) (optional) enable sensitive data redaction https //docs resolve ai/sensitive data redaction click save connect via satellite save the dynatrace access token and platform token in a kubernetes secret, then update the resolve satellite to use this secret 1 create kubernetes secret create a kubernetes secret using this structure secret creation apiversion v1 kind secret type opaque metadata name dynatrace resolve token stringdata apitoken "\<your access token>" apptoken "\<your platform token>" security best practice never store credentials in plaintext in configuration files or source control always use kubernetes secrets and encrypt etcd or use enterprise secret management systems see secret management docid kane7 hr5yzbf mb 4jy for detailed guidance apply the secret apply secret kubectl apply f dynatrace resolve token yml 2 update values file add the dynatrace integration to resolve values yaml resolve values yaml integrations dynatrace type "dynatrace" create true secretname "dynatrace resolve token" connection apiurl https //abc12345 live dynatrace com appurl https //abc12345 apps dynatrace com (optional) add sensitive data redaction https //docs resolve ai/sensitive data redaction with redactionconfig resolve values yaml integrations dynatrace type "dynatrace" create true secretname "dynatrace resolve token" connection apiurl https //abc12345 live dynatrace com appurl https //abc12345 apps dynatrace com redactionconfig enabled true 3 apply changes update the satellite with the new resolve values yaml file helm upgrade install resolve satellite \\ oci //registry 1 docker io/resolveaihq/satellite chart \\ \ values resolve values yaml 4 verify integration open dynatrace integration https //app0 resolve ai/integrations/dynatrace/connect and check the connection what resolve ingests once connected, resolve continuously ingests the following from dynatrace infrastructure entities — hosts, services, processes, and smartscape topology used to build the service map alert rules — dynatrace metric events and problem patterns problems — open and historical dynatrace problems, used as alerts during investigations logs — queried on demand via grail using the dynatrace query language (dql) metrics — queried on demand using the dynatrace metric selector language dashboards — platform dashboards (documents api) are loaded for chart level context during investigations