Skip to main content

Configure Dynatrace to Send Webhooks

Configure Dynatrace to send webhook notifications to Harness AI SRE when problems are detected.

Before you begin

  • Harness webhook endpoint: Create a Dynatrace webhook in Harness AI SRE using the Dynatrace webhook template.
  • Dynatrace permissions: Access to configure problem notifications and integrations.
  • Webhook URL: Copy the webhook URL from your Harness webhook configuration.
  • Dynatrace webhook documentation: Go to Problem Notifications to understand notification configuration.
  • Webhook integration reference: Go to Webhook Integration for webhook-specific setup.

Create webhook notification in Dynatrace

  1. In Dynatrace, go to SettingsIntegrationProblem notifications
  2. Click Add notification
  3. Select Custom integration

Configure webhook

Configure these fields:

  • Display name: Harness AI SRE
  • Webhook URL: Your Harness webhook URL
  • Notification settings: Configure when to call the webhook
    • Call the webhook when new events merge into an existing problem
    • Notify the webhook when a problem closes (in addition to the default open-problem notification)

Test the notification

  1. Click Send test notification
  2. Verify the test appears in Harness AI SRE
  3. Click Save to activate the notification

Configure field mapping in Harness

Map Dynatrace problem fields to Harness alert properties.

Basic field mapping

title: "{{webhook.ProblemTitle}}"
message: |
{{webhook.ProblemDetails}}

Impacted Entity: {{webhook.ImpactedEntity}}
severity: |
webhook.ProblemSeverity == "ERROR" ? "critical" :
webhook.ProblemSeverity == "WARNING" ? "high" :
webhook.ProblemSeverity == "RESOURCE_CONTENTION" ? "medium" : "low"
source: "dynatrace"
link: "{{webhook.ProblemURL}}"
tags:
- "source:dynatrace"
- "problem_id:{{webhook.ProblemID}}"
- "state:{{webhook.State}}"

Advanced filtering

// Only process open problems
filter: webhook.State == "OPEN"

// Filter by severity
filter: webhook.ProblemSeverity in ["ERROR", "WARNING"]

// Filter by impacted entity type
filter: webhook.ImpactedEntity.contains("SERVICE")

Available Dynatrace fields

FieldDescriptionExample
StateProblem stateOPEN, RESOLVED
ProblemIDUnique problem identifier-1234567890123456789_1234V2
ProblemTitleProblem summaryResponse time degradation
ProblemDetailsDetailed descriptionResponse time increased by 200%
ImpactedEntityAffected entity nameSERVICE-ABC123
ProblemSeveritySeverity levelERROR, WARNING
ProblemURLLink to problem in Dynatracehttps://abc123.live.dynatrace.com/...
TagsAssociated tagsenvironment:production

Troubleshooting

Webhook not triggering

Cause: Notification not configured or problem not matching filters.

Solution:

  • Verify notification is enabled in Dynatrace
  • Check that problem severity matches your filter criteria
  • Use "Send test notification" to verify webhook URL
  • Review Dynatrace notification logs

Problems not creating alerts

Cause: Field mapping mismatch or filtering rules blocking alerts.

Solution:

  • Check CEL filter expressions allow the problem through
  • Verify required fields (title, message) are mapped
  • Test with a simpler payload first
  • Review Harness webhook logs for errors

Duplicate alerts for same problem

Cause: Multiple problem state changes triggering separate webhooks.

Solution:

  • Use problem ID for deduplication in route alerts
  • Configure Dynatrace to only send "Open problems" notifications
  • Add CEL filter: webhook.State == "OPEN"

Next steps


Further reading

Dynatrace Official Documentation