Skip to main content
Integrate Aurora with Dynatrace to receive problem notifications, analyze performance issues, and leverage AI-driven root cause analysis across your entire stack.

Authentication

Dynatrace uses API Token authentication with your environment URL.

Prerequisites

  • Dynatrace environment (SaaS or Managed)
  • Permissions to create API tokens

Setup Steps

1

Create API Token

  1. Go to your Dynatrace environment (e.g., https://abc12345.live.dynatrace.com)
  2. Navigate to Settings > Integration > Dynatrace API
  3. Click Generate token
  4. Name: Aurora
  5. Required scopes:
    • apiTokens.read - Token validation
    • ReadConfig - Read configuration (optional but recommended)
  6. Click Generate and copy the token
2

Get Environment URL

Your Dynatrace environment URL follows this format:
  • SaaS: https://{env-id}.live.dynatrace.com
  • Managed: https://{your-domain}/e/{environment-id}
Aurora automatically converts .apps.dynatrace.com URLs to .live.dynatrace.com (API domain).
3

Connect to Aurora

  1. In Aurora, navigate to Integrations > Dynatrace
  2. Enter your environment URL
  3. Paste your API token
  4. Click Connect

Configuration

No environment variables are required. API tokens are entered through the Aurora UI.

Supported Environments

  • SaaS: https://{env-id}.live.dynatrace.com
  • Managed: https://{domain}/e/{env-id}
  • Gov Cloud: Custom domains

Webhook Setup

Receive real-time problem notifications from Dynatrace:
1

Get Webhook URL

In Aurora’s Dynatrace integration page, copy your webhook URL:
2

Create Custom Integration (Classic UI)

  1. Go to your Dynatrace environment
  2. Open the classic UI: https://{env-id}.live.dynatrace.com/ui/settings/integration/notifications
  3. Click Add notification
  4. Select Custom Integration
  5. Name: Aurora
  6. Webhook URL: Paste your Aurora webhook URL
3

Configure Payload

Use this custom payload template for Aurora (or copy from the integration page):
4

Test and Save

  1. (Optional) Assign an Alerting Profile to filter problems
  2. Click Send test notification to verify connectivity
  3. Save the integration

Development with ngrok

For local development:
.env
Start ngrok:

What Aurora Can Query

Once connected, Aurora can:

Connection Status

  • Verify API token validity
  • View environment URL
  • Check Dynatrace cluster version
API Endpoint: GET /dynatrace/status Response:

Webhook Problems

  • Receive real-time problem notifications
  • Auto-create incidents from Dynatrace problems
  • Track problem state transitions (OPEN, RESOLVED)
  • Monitor problem impact and severity
  • Correlate related problems
  • Generate AI-powered root cause analysis
Ingested Data:
  • Problem ID and title
  • Problem state (OPEN, RESOLVED)
  • Severity level (AVAILABILITY, ERROR, PERFORMANCE, etc.)
  • Impact level (APPLICATION, SERVICE, INFRASTRUCTURE)
  • Impacted entities
  • Problem URL for deep linking
  • Tags and metadata
API Endpoint: GET /dynatrace/alerts Parameters:
  • limit - Number of problems (default: 50)
  • offset - Pagination offset (default: 0)
  • state - Filter by state (OPEN, RESOLVED)
Response:

RCA Settings

  • Enable/disable automated root cause analysis for Dynatrace problems
  • Per-user preference stored in Aurora
API Endpoints:
  • GET /dynatrace/rca-settings - Get current RCA settings
  • PUT /dynatrace/rca-settings - Update RCA settings
Request:
Response:

Troubleshooting

Connection Failed
  • Verify API token is correct and not expired
  • Check token has required scopes (apiTokens.read)
  • Ensure environment URL is correct
  • For Managed: verify Aurora can reach your Dynatrace instance
Invalid Environment URL
  • Use the .live.dynatrace.com domain (not .apps.)
  • Include /e/{environment-id} for Managed deployments
  • Ensure URL uses HTTPS
  • Remove trailing slashes
Webhook Not Receiving Problems
  • Verify NGROK_URL is set correctly (local development)
  • Ensure ngrok tunnel is running
  • Check webhook URL in Dynatrace matches Aurora UI
  • Send test notification from Dynatrace integration settings
  • Verify payload template matches suggested format
“Connection timed out”
  • Check network connectivity between Aurora and Dynatrace
  • Verify firewall rules allow outbound HTTPS
  • For Managed: ensure Dynatrace instance is reachable from Aurora
Missing Problem Details
  • Ensure custom payload template includes all fields
  • Check that Dynatrace placeholders (e.g., {ProblemID}) are correct
  • Verify problem contains expected metadata

API Reference

Base Path: /dynatrace For detailed Dynatrace API documentation, see: