Skip to main content

We use cookies for essential site functions and anonymous analytics. Choose what to allow.

Accepts all cookies and closes this banner
Reject All
Observability Integration Guide

Dynatrace Alerts in Slack & Microsoft Teams

KM

Kumar Makala · Founder & CEO, SyncRivo

Kumar Makala leads platform engineering and technical content at SyncRivo, focused on enterprise messaging interoperability, messaging bridge architecture, and cross-platform integration patterns across Slack, Microsoft Teams, Google Chat, Zoom Team Chat, and Cisco Webex. LinkedIn

Updated · 10 min read

Dynatrace Hub ships both a Slack integration and a Teams integration. Each posts alerts to its own platform, so teams on both platforms enable both.

SyncRivo does not relay bot or app messages — it bridges the human conversation, so people on Slack and Teams can discuss the alert together in one bridged channel.

Dynatrace Event Types in Slack & Teams

Problem opened, resolved, deployment events, availability alerts, and security findings — posted by Dynatrace's native Slack and Teams integrations.

Problem Opened

Dynatrace anomaly and problem open events — error rate spikes, response time degradation, availability drops — posted by the Dynatrace Slack and Teams integrations to the channels you configure in Dynatrace.

Problem Resolved

Problem resolved events posted by the native integrations to the same channels that received the open alert, closing the incident loop.

Deployment Event

Deployment marker events posted to a release channel — useful for correlating deployments with performance changes.

Custom Alert Triggered

Custom metric threshold alerts (error budget burn rate, p99 latency breach, SLO violation) posted to the SRE on-call channel by the native integration you configure.

Availability Alert

Service or synthetic monitor availability alerts posted to on-call channels by Dynatrace. With SyncRivo bridging the discussion channel, responders on Slack and Teams coordinate in one conversation.

Security Vulnerability Detected

Dynatrace Application Security vulnerability detection events posted to the security team channel by the native integration.

How to Route Dynatrace Alerts to Slack & Teams

Notifications come from Dynatrace's native integrations; SyncRivo bridges the discussion.

  1. 1
    Enable the Dynatrace Slack integration
    In Dynatrace Hub, install the Slack integration and choose the Slack channel for problem notifications.
  2. 2
    Enable the Dynatrace Teams integration
    In Dynatrace Hub, install the Microsoft Teams integration and choose the Teams channel for problem notifications.
  3. 3
    Configure Dynatrace problem notifications
    In Dynatrace, go to Settings → Integration → Problem notifications. Configure the event filter (problem severity, entity tags) for each integration.
  4. 4
    Connect Slack and Teams to SyncRivo
    Connect your Slack workspace and Microsoft Teams tenant to SyncRivo. Workspace and tenant admins approve the apps.
  5. 5
    Bridge the incident discussion channel
    Bridge the channel where responders discuss incidents. Human replies sync both ways; the Dynatrace bot posts themselves are not relayed.

Dynatrace → Messaging Platform Channel Layout

Example channel layout configured in Dynatrace's native Slack and Teams integrations, for SRE and operations teams on mixed Slack and Teams environments.

Dynatrace EventNative Integration Posts ToResult
Problem Opened (AVAILABILITY)→ Slack #on-call + Teams #engineering-leadershipSeparate native integrations notify each platform; discussion can be bridged by SyncRivo
Problem Opened (PERFORMANCE)→ Slack #sre-teamPerformance degradation surfaced to SRE team on their platform
Problem Resolved→ Slack #on-call + Teams #engineering-leadershipIncident closure posted by each native integration
Deployment Event→ Teams #releases + Slack #engineeringDeployment correlated with performance data across teams
Custom Alert (SLO breach)→ Slack #on-call + Teams #sre-leadsSLO breach posted to on-call and leads by each native integration
Security Vulnerability Detected→ Slack #security + Teams #leadershipSecurity finding reaches technical and leadership audiences

Dynatrace Native Integrations vs SyncRivo

CapabilityDynatrace NativeSyncRivo
Notify Slack✓ Dynatrace Hub Slack integration— Not relayed (SyncRivo does not relay bot or app posts)
Notify Microsoft Teams✓ Dynatrace Hub Teams integration — configured independently from Slack— Not relayed; use the native integration
Human discussion across Slack, Teams, Webex, Google Chat, Zoom✗ Not available✓ Bridged channels, threads, edits and files
SetupConfigured in Dynatrace per platformFirst channel bridge typically live during onboarding, after admin approval

Frequently Asked Questions

Does Dynatrace have a Microsoft Teams integration?▾

Dynatrace has both a Slack integration and a Microsoft Teams integration available in the Dynatrace Hub. Both are official integrations. They operate independently — the Slack integration posts anomaly and problem notifications to a Slack channel; the Teams integration posts notifications to a Teams channel. For SRE and operations teams spanning both platforms, enable both native integrations. SyncRivo does not relay bot or app messages, so it does not forward Dynatrace notifications; it bridges the human conversation, so people on Slack and Teams can discuss the problem together in one bridged channel.

How do I send Dynatrace alerts to Microsoft Teams and Slack at the same time?▾

Configure both of Dynatrace's native integrations: the Slack integration for your Slack channel and the Teams integration for your Teams channel. SyncRivo does not accept webhooks from Dynatrace and does not route alerts. Its role is to bridge the human discussion that follows between Slack, Teams, Google Chat, Webex, and Zoom Team Chat.

What Dynatrace events can SyncRivo route to messaging platforms?▾

None — SyncRivo does not route Dynatrace events. Dynatrace's own Slack and Teams integrations deliver events such as Problem Opened, Problem Resolved, deployment events, custom alerts, availability alerts, and security findings. Messages posted by bots or apps are not relayed by SyncRivo; it bridges the messages people write, so the incident conversation stays in sync across chat platforms.

How does Dynatrace problem notification routing work with SyncRivo?▾

Dynatrace problem notifications are configured entirely in Dynatrace: you choose the integration (Slack, Teams, or webhook), the severity filters (AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION), and the destination channel. SyncRivo is not part of that path. Once the notification lands, SyncRivo can bridge the channel where engineers discuss it, so replies from Slack users appear in Teams and vice versa.

Can SyncRivo help during an M&A when teams use different messaging platforms?▾

Yes, for the human conversation. When an acquired operations team uses Teams while yours uses Slack, point each Dynatrace native integration at the channel each team uses, and use SyncRivo to bridge an incident channel between Slack and Teams so both teams can coordinate in one conversation. SyncRivo does not forward the Dynatrace notification itself.

What is the difference between Dynatrace Hub integrations and SyncRivo for messaging?▾

They do different jobs. Dynatrace Hub Slack and Teams integrations post Dynatrace notifications into each platform. SyncRivo is a messaging interoperability platform that bridges human conversations between Slack, Teams, Google Chat, Webex, and Zoom Team Chat — it does not relay bot or app messages, so it complements rather than replaces the native integrations.

Keep the Incident Conversation in Sync

Dynatrace's native integrations post the alerts. SyncRivo bridges the human discussion, so responders on Slack and Teams work the incident together.

cookie_consent.banner.aria_announcement