Dynatrace Has Both a Slack and a Teams Integration. They Route Independently.

Dynatrace Hub ships both a Slack integration and a Microsoft Teams integration. Both are official, Dynatrace-maintained integrations. You configure them in Settings → Integration → Problem notifications — select Slack, fill in the bot token and channel; select Teams, fill in the Teams webhook URL and channel.

Both integrations work. Each routes Dynatrace problem notifications to its configured platform. A problem opened event fires the Slack notification. A separate Teams notification rule fires the Teams notification.

They are completely independent. The same P1 availability alert does not automatically notify both platforms from a single notification rule. You maintain two separate configurations — two sets of channel mappings, two sets of event filters, two authentication tokens — to cover a mixed Slack/Teams operations team.

The Operational Problem

For a uniform SRE team all on Slack, the Slack integration is sufficient. For a uniform operations team all on Teams, the Teams integration is sufficient.

For the majority of enterprise organizations — where SRE engineers are on Slack, engineering managers are on Teams, DevOps leads are on Webex, and the CTO uses Google Chat — maintaining separate Dynatrace notification rules per platform becomes a configuration maintenance burden.

More critically: when you have separate notification rules, they can drift. Channel names change, bot tokens expire, filter configurations diverge. The on-call Slack channel gets the P1 alert; the engineering leadership Teams channel was misconfigured six months ago and hasn't received an alert since.

The SyncRivo Approach

Configure a single Dynatrace outbound webhook notification rule (Settings → Integration → Problem notifications → Webhook) pointing to SyncRivo. SyncRivo receives the Dynatrace problem payload and routes to every platform in your configuration simultaneously — Slack, Teams, Webex, Google Chat, Zoom — with per-severity routing rules.

One Dynatrace notification rule. One SyncRivo endpoint. All platforms notified simultaneously.

Severity-Based Routing

In SyncRivo, routing rules can filter on the Dynatrace problem severity field:

• AVAILABILITY (highest severity): Slack #on-call + Teams #engineering-leadership simultaneously
• ERROR (high severity): Slack #sre-team + Teams #engineering-leads
• PERFORMANCE (medium severity): Slack #sre-team only
• RESOURCE_CONTENTION (lower severity): Slack #sre-team only, no Teams escalation

This removes the need for multiple Dynatrace notification rules with different severity filters — the routing logic lives in SyncRivo, not in Dynatrace.

Problem Resolved Routing

Dynatrace fires a separate notification when a problem resolves. SyncRivo routes the resolved event to the same channels that received the open alert — closing the incident loop across platforms without manual follow-up posts.

For the complete Dynatrace webhook setup, severity-based routing configuration, and multi-platform observability alerting matrix, see the Dynatrace Alerts in Slack & Teams integration guide.