Upgrade team-based and global alerting

Latest Dynatrace
Upgrade guide
Published Jul 24, 2026

The following alerting configurations must be upgraded to Latest Dynatrace: problem notifications, security notifications, and enterprise-grade integrations such as ServiceNow or PagerDuty. Each moves from static channel configuration to event-driven Workflows.

Why upgrade?

Replacing static notification channels with event-driven Workflows gives teams conditional logic, branching, and native API integrations, and consolidates the hundreds of classic alerting profile pairs that the latest platform model no longer needs.

Event-driven alerting workflows: conditional logic, branching, and native API integrations replace static notification channels
Security notification orchestration: granular conditions, broader external tool integration, and greater flexibility in action orchestration

What will you do?

Do not start design until the AP and PN assessment notebook has run on the environment. The assessment reveals how many classic configurations actually consolidate into workflows, and significantly changes the effort estimate.

Convert classic problem notifications and security alerting profiles to Workflows
Redesign enterprise ITSM integrations (ServiceNow, PagerDuty) as full workflows
Validate notification delivery end-to-end
Decommission classic notification configurations

Before you begin

At a glance

Estimated effort: 5–15 days
Estimated timeline: 2–6 weeks

Prerequisites

Key stakeholders

Role	Involvement	Responsibility
Dynatrace Admin	Required	Builds and configures notification workflows and connector credentials
Application Team Leads	Recommended	Validate that team-level notifications reach the correct channels with expected content
IT Operations	Recommended	Own enterprise ITSM integrations and validate bidirectional workflow behavior
Security Team	Optional	Confirms security notification workflows meet alerting and compliance requirements

Upgrade your team-based and global alerting

1. Convert problem and security notifications to workflows

Migrate classic problem notifications and security alerting profiles to workflow-based delivery with equivalent filtering, conditions, and action logic.

List all active classic problem notification integrations: channel type, filtering rules, and linked alerting profiles.
List all active security alerting profiles: conditions, severity filters, and notification targets.
For each problem notification, create an equivalent Workflow triggered by a Davis problem event with the same filtering logic.
For each security alerting profile, create an equivalent Workflow triggered by a security event with equivalent conditions.
Configure the notification action (email, MS Teams, webhook, or other channel) within each workflow.

Verify: Ratio of classic problem notification channels vs. workflow-based equivalents at target coverage; all security alerting profiles migrated.

2. Redesign enterprise integrations as full workflows

Rebuild ServiceNow, PagerDuty, and other ITSM integrations using Workflow connectors with conditional branching and payload transformation.

Document the current behavior of each ITSM integration: event types, field mappings, escalation logic, and bidirectional sync requirements.
Identify the relevant Workflow connector for each ITSM tool (ServiceNow, PagerDuty, Jira, email).
Configure connector credentials and API access for each tool; this may require IT Operations approval.
Build each ITSM integration as a Workflow: define the trigger, add conditional branching for event severity or type, and configure the connector action with the required field mappings.
Test each workflow with a simulated event to confirm correct payload delivery and bidirectional behavior where applicable.

Verify: Ratio of classic ITSM integrations (ServiceNow, PagerDuty, and others) rebuilt as Latest Dynatrace Workflows at target coverage.

Plan dedicated time for ITSM integration redesign: ServiceNow bidirectional sync and PagerDuty escalation policies require full Workflow redesign, not a simple settings migration. Plan dedicated time with IT Operations for this.

Request connector credentials before starting: Workflow connectors for ServiceNow, PagerDuty, and email require credential configuration and API access that may need IT Operations approval. Initiate access requests before starting this stage.

3. Validate notification delivery end-to-end

Trigger test events to confirm each workflow delivers notifications to the correct channels with expected content and timing before decommissioning classic configurations.

For each converted workflow, trigger a test event using a simulated problem or security event.
Confirm that the notification reaches the correct channel (email inbox, Teams channel, ITSM ticket) with the expected content.
For ITSM integrations with bidirectional sync, confirm that status updates in the ITSM tool are reflected in Dynatrace.
Have the owning team confirm that the received notification meets their operational needs.
Address any delivery or content issues before proceeding to decommission.

Verify: All notification workflows deliver test events successfully; owning teams confirm content and timing meet expectations.

4. Decommission classic notification configurations

Disable classic problem notifications and security alerting profiles once all workflow equivalents are validated.

For each validated Workflow, disable the corresponding classic notification integration.
Disable the corresponding classic security alerting profile once the security notification Workflow is confirmed.
Track the ratio of classic vs. Latest Dynatrace notification configurations until target decommission is reached.
Archive or remove classic notification settings from the environment to prevent accidental re-use.

Verify: All classic problem notification channels and security alerting profiles disabled; no active notification traffic flowing through classic channels.

Stage complete when:

All classic problem notification channels and security alerting profiles have workflow-based equivalents
All notification workflows deliver test events successfully and owning teams confirm content and timing
All classic notification configurations and ITSM integrations are disabled and no active notification traffic flows through classic channels

With all alerting migrated to workflow-based delivery, the next step is to complete the entity model migration. Upgrade remaining entities & metrics updates any DQL queries across dashboards, alerts, and workflows that still reference classic entity types, completing the transition to the Smartscape 2.0 entity model.

Documentation and best practices

The following resources support your work in this stage. Documentation covers platform concepts, configuration reference, and related guides; best practice cards provide implementation guidance from Dynatrace experts.

Upgrade from Classic problem notification to simple workflows

Guide for migrating classic problem notifications and alerting configurations to workflow-based delivery.
Best practices for upgrading alerting profiles and problem notifications to workflows

Migrate classic problem notifications and alerting profiles to event-driven Dynatrace Workflows with equivalent filtering and delivery logic.
Best practices for upgrading security notifications

Migrate classic security alerting profiles to Dynatrace Workflows with granular conditions and external tool integrations.

Ready for more?

When all notification workflows are validated and classic channels are decommissioned, you're ready to complete the entity model migration. Upgrade remaining entities & metrics updates DQL queries across dashboards, alerts, and workflows that still reference classic entity types, a targeted step that closes out the core configuration migration.