Dashboard
Platform

AppDynamics Health Check

For AppDynamics, you need to add the base URL and API key header to be used against the AppDynamics API. For the base URL, use this format: <span class="code-class-custom">https://<your_domain>.sass.appdynamics.com</span>. You can copy or create the API key header in the AppDynamics app. See API Clients in the AppDynamics documentation for details.

To add an AppDynamics health check:

  1. Open the Health Checks page in the Gremlin web app, click + Health Check, then select AppDynamics from the Integrations drop-down.
  2. If you've already authenticated AppDynamics, continue to step 3. Otherwise, follow these steps:
  3. ^Add the base URL for your AppDynamics integration using this format: https://<your_domain>.sass.appdynamics.com
  4. ^From the AppDynamics web app, create a new API key or copy an existing one.
  5. ^In the Authentication section, paste the API key into the corresponding box.
  6. ^In the Authentication section, paste the API key into the corresponding box.
  7. ^Click Authenticate Observability Tool. To validate the endpoint with the added header, Gremlin calls the following API: https://${domainName}.saas.appdynamics.com/controller/rest/applications/
  8. ^If the authentication passes, click Save Authentication.
  9. Click Next.
  10. Enter a name for the health check in the Health Check Name box.
  11. In the AppDynamics web app, navigate to the Applications tab and select your app. Then, enter the application URL in the Application URL field in the Gremlin web app. For example: https://example.saas.appdynamics.com/controller/#/location=APP_DASHBOARD&timeRange=last_1_hour.BEFORE_NOW.-1.-1.60&application=1042798&dashboardMode=force
    Note
    The Application URL must point to an Application entity relevant to the Service you are creating in Gremlin. You can get this from the Applications tab in the AppDynamics web app. See Alert and Respond in the AppDynamics documentation for more information.
  12. Click Test Health Check. Gremlin will query /problems/healthrule-violations AppDynamics API for existing health-rule violations, using the application entity ID from the input URL.
  13. ^
    If the monitor is OK, the response will look similar to this:
  14. ^If the monitor is in another state like Alert, Ignored, No Data, Skipped, Unknown, or Warn, you can still save the Health Check, but it will not evaluate to successful once a Reliability Test is run, impacting the Service's Reliability Score.
  15. Click Create 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
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
Alfi
Additional Configuration for Helm
Amazon CloudWatch Health Check
AppDynamics Health Check
Application Level Fault Injection (ALFI)
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
Role Based Access Control
Running Failure Flags experiments
Scheduling Scenarios
Shared Scenarios
Shutdown Experiment
Slack
Teams
Time Travel Experiment
Troubleshooting Gremlin on OpenShift
User Authentication via SAML and Okta
Users
Webhooks
Integration Agent for Linux
Test Suites
Restricting Testing Times
Reports
Process Exhaustion Experiment
Enabling DNS collection