Automate Runbooks with Dynatrace Workflow Triggers (2026)

You can trigger automated workflows in Dynatrace based on any event that happens in your environment, not just alerts.

Let’s say you want to automatically create a Jira ticket when a new Kubernetes pod enters a CrashLoopBackOff state. Here’s how you’d set that up.

First, we need a Dynatrace Alerting Profile. This isn’t for alerting in the traditional sense, but for defining what events we want to react to.

Go to "Alerting" -> "Alerting profiles" -> "Add profile".

Name it something descriptive, like KubernetesCrashLoopBackOffTrigger.

Now, we define the conditions. Under "Conditions", click "Add condition". We’ll select "Kubernetes Pod State" and set the condition to "is CrashLoopBackOff". For "Scope", select your specific cluster or namespace if you want to narrow it down.

Next, we need to configure the "Announce" section. This is where we tell Dynatrace what to do when the condition is met. Under "Announce", select "Send a custom notification". We’ll choose "Webhook" as the notification type.

Now, for the actual workflow. Go to "Automations" -> "Workflows" -> "Create workflow".

Name it something like CreateJiraForPodCrash.

Under "Trigger", select "Alerting event". In the "Alerting profile" dropdown, choose the profile we just created: KubernetesCrashLoopBackOffTrigger.

Now, under "Actions", click "Add action". Select "Send a webhook request".

This is where we’ll configure the Jira integration. For "URL", you’ll need your Jira webhook URL. This typically looks like https://your-jira-domain.atlassian.net/rest/webhooks/latest/general/your-webhook-id. For "Method", select POST. For "Headers", add Content-Type: application/json. For "Body", we’ll construct the JSON payload for Jira. This is where you’ll dynamically pull information from the Dynatrace event.

Here’s a sample JSON body for creating a Jira issue:

{
  "fields": {
    "project": {
      "key": "YOUR_PROJECT_KEY"
    },

    "summary": "Pod in CrashLoopBackOff: {{dt.event.kubernetes.pod.name}} in {{dt.event.kubernetes.namespace}}",


    "description": "A Kubernetes pod has entered the CrashLoopBackOff state.\n\nPod Name: {{dt.event.kubernetes.pod.name}}\nNamespace: {{dt.event.kubernetes.namespace}}\nNode: {{dt.event.kubernetes.node.name}}\nReason: {{dt.event.kubernetes.pod.reason}}\n\n[View in Dynatrace]( {{dt.event.url}} )",

    "issuetype": {
      "name": "Bug"
    }
  }
}

You’ll replace "YOUR_PROJECT_KEY" with your actual Jira project key.

The {{dt.event...}} placeholders are Dynatrace’s way of injecting context from the triggering event into your webhook payload. Dynatrace provides a rich set of these variables for different event types. You can explore them in the workflow editor’s context pane.

For the Jira webhook to work, you’ll need to configure a corresponding incoming webhook in your Jira project settings. Go to "Jira Settings" -> "System" -> "Webhooks" -> "Create a Webhook". Paste your Dynatrace workflow’s webhook URL there.

This setup leverages Dynatrace’s powerful event-driven automation. Instead of waiting for a user to see an alert and manually create a ticket, Dynatrace proactively detects the CrashLoopBackOff state and immediately initiates the Jira ticket creation process. This drastically reduces the Mean Time To Resolution (MTTR) by ensuring that issues are logged and triaged the moment they occur.

The true power here is in the dynamic data injection. You’re not just creating a generic ticket; you’re populating it with specific, real-time details about the failing pod, its namespace, and even a direct link back to the relevant Dynatrace problem for immediate investigation.

The next step you’ll likely want to automate is acknowledging the problem within Dynatrace itself once the Jira ticket is created, preventing duplicate notifications.