Dashboard
Platform

Dynatrace Health Check

Adding a Dynatrace Health Check requires the following steps:

  1. Identify your Dynatrace instance ID
  2. Identify the entity in Dynatrace that you want to use for the Health Check
  3. Format the entity URL using the entity ID
  4. Set up the Health Check in Gremlin

Identifying your Dynatrace instance ID

First, you'll need your Dynatrace instance ID. This uniquely identifies your Dynatrace account.

Navigate to your Dynatrace instance in a web browser. The start of the URL will look similar to this: https://qpm46186.live.dynatrace.com/. The first part of the URL is your Dynatrace instance ID. In this example, the instance ID is qpm46186.

Keep this instance ID handy for later reference.

Identifying the Dynatrace entity you want to use for the Health Check

Next, you'll need the ID of the Dynatrace entity (the entity ID) you want to monitor. These instructions will vary depending on whether your service is a host or a Kubernetes resource.

Host-based Health Checks

  1. In the Dynatrace web app, click on the Hosts link in the sidebar, then click on the name of the host you want to monitor.
  2. Once the host details screen has loaded, copy the relevant entity ID from your browser’s URL bar. In the screenshot below, the entity ID is highlighted in red.
Retrieving the Dynatrace entity ID for a host

Kubernetes-based Health Checks

  1. In the Dynatrace web app, click on the Kubernetes link in the sidebar, then click on the Kubernetes cluster you want to monitor.
  2. On the cluster details screen, click on the namespace where your Kubernetes object is deployed.
  3. Click on the name of the Kubernetes object that you want to monitor.
  4. Once the object’s details screen has loaded, copy the relevant entity ID from your browser’s URL bar. In the screenshot below, the entity ID is highlighted in red.
Retrieving the Dynatrace enttiy ID for a Kubernetes resource

Formatting the Dynatrace entity URL

Once you have your Dynatrace instance ID and entity ID, you can create the API call for the Gremlin Health Check. Use the following URL, replacing INSTANCE_ID with your Dynatrace instance ID, and ENTITY_ID with your Dynatrace entity ID:

https://INSTANCE_ID.live.dynatrace.com/api/v2/problems?problemSelector=status("open")&entitySelector=entityId("ENTITY_ID")

Creating the Health Check in Gremlin

Before creating the Health Check, you'll need to authenticate your Gremlin account with Dynatrace. This is a one-time step per Gremlin team. Once the authentication is saved, it becomes available to your entire Gremlin team. If you or someone else in your Gremlin team has already authenticated with Dynatrace, you can skip this section and go directly to Creating a Dynatrace Health Check.

Authenticating with Dynatrace

To authenticate with Dynatrace in Gremlin:

  1. Open the Health Checks page in the Gremlin web app, click + Health Check, then select Dynatrace from the Integrations drop-down.
  2. Enter the API base URL for your Dynatrace account. Replace INSTANCE_ID with the actual ID of your Dynatrace instance: https://INSTANCE_ID.live.dynatrace.com/
  3. In the Dynatrace web app, copy or create an API key. This key will require read permissions for both the problems API and the synthetics API.
  4. Back in the Gremlin web app, under Authentication, paste the API key into the API Key box.
  5. Click Authenticate Observability Tool to send a test request. If Gremlin successfully receives a response, click Save Authentication.

A successful authentication will look similar to the following screenshot:

Screenshot of a successful Dynatrace authentication in Gremlin

Creating a Dynatrace Health Check

Now that you've authenticated, you can create your Health Check:

  1. Open the Health Checks page in the Gremlin web app, click + Health Check, then select Dynatrace from the Integrations drop-down and click Next.
  2. Enter a meaningful Name for the Health Check. As a best practice, the name should accurately indicate what the Health Check is monitoring.
  3. Retrieve the entity URL you created previously, and paste it into the Entity URL field. For example: https://INSTANCE_ID.live.dynatrace.com/api/v2/problems?problemSelector=status("open")&entitySelector=entityId("ENTITY_ID")
  4. Click Test Health Check. Gremlin will query Dynatrace using the instance ID, entity ID, and API key you provided.
  5. If Gremlin successfully connects to the monitor, you can save the Health Check by clicking Create Health Check. You can now add this Health Check to any Scenario or Service in your Gremlin team.
Creating and saving a Dynatrace Health Check
No items found.
Next
Previous
This is some text inside of a div block.
Compatibility
Installing the Gremlin Agent
Authenticating the Gremlin Agent
Configuring the Gremlin Agent
Managing the Gremlin Agent
User Management
Integrations
Health Checks
Notifications
Command Line Interface
Updating Gremlin
Reliability Management (RM) Quick Start Guide
Services and Dependencies
Detected Risks
Reliability Tests
Reliability Score
Targets
Experiments
Scenarios
GameDays
Overview
Deploying Failure Flags on AWS Lambda
Deploying Failure Flags on AWS ECS
Deploying Failure Flags on Kubernetes
Classes, methods, & attributes
API Keys
Examples
Container security
General
Linux
Windows
Chao
Helm
Glossary
Additional Configuration for Helm
Amazon CloudWatch Health Check
AppDynamics Health Check
Blackhole Experiment
CPU Experiment
Certificate Expiry
Custom Health Check
Custom Load Generator
DNS Experiment
Datadog Health Check
Disk Experiment
Dynatrace Health Check
Grafana Cloud Health Check
Grafana Cloud K6
IO Experiment
Install Gremlin on Kubernetes manually
Install Gremlin on OpenShift 4
Installing Gremlin on AWS - Configuring your VPC
Installing Gremlin on Kubernetes with Helm
Installing Gremlin on Windows
Installing Gremlin on a virtual machine
Installing the Failure Flags SDK
Jira
Latency Experiment
Memory Experiment
Network Tags
New Relic Health Check
Overview
Overview
Overview
Overview
Overview
Packet Loss Attack
PagerDuty Health Check
Preview: Gremlin in Kubernetes Restricted Networks
Private Network Integration Agent
Process Collection
Process Killer Experiment
Prometheus Health Check
Configuring Role Based Access Control (RBAC)
Running Failure Flags experiments
Scheduling Scenarios
Shared Scenarios
Shutdown Experiment
Slack
Managing Teams
Time Travel Experiment
Troubleshooting Gremlin on OpenShift
User Authentication via SAML and Okta
Managing Users
Webhooks
Integration Agent for Linux
Test Suites
Restricting Testing Times
Reports
Process Exhaustion Experiment
Enabling DNS collection
Authenticating Users with Microsoft Entra ID (Azure Active Directory) via SAML
AWS Quick Start Guide