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

New Relic 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

New Relic's native notification channels post alerts to Slack and Teams. SyncRivo bridges the human discussion between chat platforms, so SRE and engineering teams on different platforms can work the same incident together.

New Relic Alert Types Sent to Slack & Teams

New Relic posts these through its own notification channels. SyncRivo does not relay bot or app messages; it bridges the human discussion.

APM Error Rate Alerts

Application error rate and Apdex threshold breaches posted to SRE and engineering channels by New Relic notification channels.

Infrastructure Alerts

CPU, memory, disk I/O, and network threshold violations on hosts and containers posted to on-call and operations channels.

Synthetic Monitor Failures

New Relic Synthetics monitor failures posted to platform engineering and reliability channels.

NRQL Custom Alerts

Custom NRQL alert conditions posted to the channels of the teams that own each metric.

AIOps Incident Alerts

New Relic Applied Intelligence incident correlations and anomaly detections posted to on-call channels.

Resolved Notifications

Alert resolution events posted to incident channels so stakeholders know the issue is cleared.

How to Route New Relic Alerts to Slack & Teams

New Relic posts the alerts; SyncRivo bridges the conversation. Your first channel bridge is typically live during onboarding, once your Slack/Teams admins approve the app.

  1. 1
    Add the New Relic Slack notification channel
    In New Relic, go to Alerts & AI → Notification Channels and add the native Slack channel for the relevant alert policies.
  2. 2
    Add the New Relic Microsoft Teams notification channel
    Add the native Microsoft Teams notification channel to the same alert policies.
  3. 3
    Connect Slack and Teams to SyncRivo
    Book a demo to start a guided pilot. Your Slack and Microsoft Teams admins approve the SyncRivo apps. SyncRivo does not relay messages posted by bots and apps such as New Relic.
  4. 4
    Bridge the channels where incidents are discussed
    Bridge the SRE Slack channel with the engineering Teams channel so both teams can discuss incidents in one conversation.
  5. 5
    Test the bridged conversation
    Post a human reply in the Slack channel and confirm it appears in the bridged Teams channel, then reply from Teams.

New Relic → Messaging Platform Routing Matrix

Example setup: New Relic notification channels post each alert; SyncRivo bridges the human discussion between the channels.

New Relic AlertNew Relic Notification Channel Posts ToResult
APM error rate breach (Critical)→ Slack #sre-alerts + Teams #engineering-incidentsSRE and leadership discuss it in the bridged channel
APM error rate breach (Warning)→ Slack #sre-alertsTeam channel only — no leadership escalation
Infrastructure CPU/memory breach→ Slack #infra-alertsInfrastructure team discusses it with on-call colleagues on other platforms
Synthetic monitor failure→ Slack #platform-eng + Teams #reliabilityUptime failure visible across SRE and platform teams
NRQL custom alert breach→ Per alert policy ownerTeam-specific routing configured in New Relic
Alert resolved (OK)→ Channels on the alert policyAll-clear posted by New Relic

New Relic Native Notifications vs SyncRivo

CapabilityNew Relic NativeSyncRivo
Alert to Slack✓ Native notification channel✗ Not relayed (use native channel)
Alert to Microsoft Teams✓ Native notification channel✗ Not relayed (use native channel)
Human discussion across Slack, Teams, Webex, Google Chat, Zoom✗ Not available natively✓ Bridged human conversation
Single alert → multiple platforms simultaneously✗ Requires one channel config per platform✗ Not relayed (use one channel per platform)
Route by team without New Relic reconfiguration✗ Requires policy changes in New Relic✗ Not offered
M&A: include an acquired team on another chat platform✗ Requires new New Relic notification channel✓ Bridge their channels into the discussion

Frequently Asked Questions

Can New Relic send alerts to Microsoft Teams?▾

Yes. New Relic has a native Microsoft Teams notification channel. SyncRivo does not relay New Relic alerts — messages posted by bots and apps are not bridged. New Relic's native Slack and Teams channels post the alerts; SyncRivo bridges the human discussion between chat platforms, so people on Slack and Teams can work the incident in one bridged channel.

How do I send New Relic alerts to Slack?▾

New Relic has a native Slack notification channel. Configure it in Alerts → Notification Channels with your Slack OAuth token. To reach both Slack and Teams, configure a native notification channel for each. SyncRivo does not relay New Relic alerts; it bridges the human conversation between Slack and Teams channels.

Can I route New Relic alerts to different teams on different messaging platforms?▾

Routing is configured in New Relic itself, per alert policy and notification channel (for example SRE in Slack, engineering leadership in Teams). SyncRivo has no alert routing rules and does not relay bot or app messages. It bridges the human discussion, so SRE on Slack and leadership on Teams can talk through the incident in one bridged channel.

Does SyncRivo support New Relic webhook notification channels?▾

No. SyncRivo does not accept inbound webhooks from New Relic or other tools, and messages posted by bots and apps are not bridged. Use New Relic's native Slack and Teams notification channels; SyncRivo bridges the human conversation between Slack, Teams, Webex, Google Chat, and Zoom Team Chat.

What types of New Relic alerts can SyncRivo route?▾

None — SyncRivo does not relay New Relic alerts. New Relic's own notification channels can send APM error rate alerts, infrastructure CPU/memory threshold alerts, browser performance alerts, synthetic monitor failure alerts, NRQL-based custom alerts, and incident resolved notifications to Slack and Teams. SyncRivo bridges the human discussion that follows.

Does SyncRivo work with New Relic Applied Intelligence (AIOps)?▾

Not directly. New Relic Applied Intelligence sends incident notifications via webhooks and native notification channels; SyncRivo does not receive or relay them, because messages posted by bots and apps are not bridged. Once the incident is posted in Slack or Teams, SyncRivo bridges the human conversation about it across platforms.

How does SyncRivo handle New Relic alert routing during M&A or platform migrations?▾

New Relic notification routing is configured per notification channel in your alert policies, and SyncRivo does not change that. When a team moves platforms (for example, from Slack to Teams after a merger), update the New Relic notification channel. SyncRivo helps with the people side: it bridges channels between the platforms so both teams can keep discussing incidents without a migration.

Bring Every Team into the New Relic Incident Discussion

New Relic posts the alerts in Slack and Teams; SyncRivo bridges the conversation between them. Book a demo for a guided pilot on your own channels.

cookie_consent.banner.aria_announcement