Alex Morgan · Principal Engineer
Alex Morgan is a principal engineer at SyncRivo, focused on platform architecture, reliability engineering, and the infrastructure powering real-time messaging interoperability. LinkedIn
April 9, 2026 · 10 min read
Route New Relic APM, infrastructure, synthetic, and NRQL alerts to every platform your SRE and engineering teams use — simultaneously. One webhook. No duplicated notification channel configuration.
Every New Relic alert type — APM, infrastructure, synthetic, NRQL, and AIOps — routed to all your messaging platforms from a single webhook endpoint.
Application error rate and Apdex threshold breaches routed to SRE and engineering channels across Slack, Teams, Webex, and Google Chat simultaneously.
CPU, memory, disk I/O, and network threshold violations on hosts and containers delivered to on-call and operations channels in real time.
New Relic Synthetics monitor failures and SLA breaches routed to platform engineering and reliability channels across messaging platforms.
Custom NRQL alert conditions fanned out to the specific teams that own each metric — SRE in Slack, leadership in Teams, partners in Google Chat.
New Relic Applied Intelligence incident correlations and anomaly detections delivered to on-call channels with full context across all platforms.
Alert resolution events broadcast to all subscribed incident channels so every stakeholder knows the issue is cleared without polling New Relic.
Setup takes under 15 minutes. No code required.
Example routing for SRE teams using New Relic across multi-platform engineering organizations.
| New Relic Alert | SyncRivo Routes To | Result |
|---|---|---|
| APM error rate breach (Critical) | → Slack #sre-alerts + Teams #engineering-incidents | SRE and leadership both notified immediately |
| APM error rate breach (Warning) | → Slack #sre-alerts | Team channel only — no leadership escalation |
| Infrastructure CPU/memory breach | → Slack #infra-alerts + PagerDuty on-call | Infrastructure alert escalated to on-call rotation |
| Synthetic monitor failure | → Slack #platform-eng + Teams #reliability | Uptime failure visible across SRE and platform teams |
| NRQL custom alert breach | → Routed per alert policy owner | Team-specific routing without New Relic reconfiguration |
| Alert resolved (OK) | → All subscribed channels | All-clear broadcast confirms issue resolved |
| Capability | New Relic Native | SyncRivo |
|---|---|---|
| Alert to Slack | ✓ Native notification channel | ✓ Via webhook relay |
| Alert to Microsoft Teams | ✓ Native notification channel | ✓ Via webhook relay |
| Alert to Webex / Google Chat / Zoom | ✗ Not available natively | ✓ All 5 platforms |
| Single alert → multiple platforms simultaneously | ✗ Requires one channel config per platform | ✓ One endpoint, fan-out to all |
| Route by team without New Relic reconfiguration | ✗ Requires policy changes in New Relic | ✓ Update routing rule in SyncRivo only |
| M&A: add acquired team's platform post-merger | ✗ Requires new New Relic notification channel | ✓ Add destination in SyncRivo in minutes |
| SOC 2 audit trail for alert delivery | ✗ Not available | ✓ Full event log per delivery |
| Decouple monitoring config from team platform choice | ✗ Tightly coupled — changing platform requires NR changes | ✓ Change platform at SyncRivo layer, NR untouched |
Yes. New Relic has a native Microsoft Teams notification channel. For routing the same New Relic alert to Teams AND Slack simultaneously — or fan-out to Webex, Google Chat, and Zoom — SyncRivo acts as a webhook routing layer. Configure a New Relic webhook notification channel pointing at SyncRivo, and SyncRivo fans the alert to all connected platforms from a single endpoint.
New Relic has a native Slack notification channel. Configure it in Alerts → Notification Channels with your Slack OAuth token. For multi-platform delivery (New Relic → Slack AND Teams simultaneously), configure a SyncRivo webhook as a New Relic notification channel — SyncRivo routes the alert to all connected messaging platforms in a single step.
Yes. With SyncRivo routing rules, a single New Relic alert policy can notify your SRE team in Slack, post to a Teams channel for engineering leadership, and optionally reach a Webex space for operations — all simultaneously. Routing is configurable per alert policy, condition priority, or incident severity.
Yes. SyncRivo accepts inbound webhooks from New Relic Alerts (both legacy alert policies and the newer NerdGraph alert conditions). In New Relic, create a Webhook notification channel and set the URL to your SyncRivo inbound webhook endpoint. SyncRivo parses the New Relic alert payload and routes it to Slack, Teams, Webex, Google Chat, or Zoom based on your configured channel mappings.
SyncRivo routes any New Relic alert that New Relic can send via webhook: APM error rate alerts, infrastructure CPU/memory threshold alerts, browser performance alerts, synthetic monitor failure alerts, NRQL-based custom alerts, and incident resolved notifications. Both legacy alert policies and the newer New Relic AI-powered alerts (AIOps) are supported.
Yes. New Relic Applied Intelligence can send incident notifications via webhooks and native notification channels. Configure a SyncRivo endpoint as a New Relic AI notification destination and SyncRivo will fan the incident alert out to Slack, Teams, and any other connected platform simultaneously — including resolved and acknowledged state changes.
New Relic notification routing is configured per notification channel in your alert policies. When a team changes platforms (for example, from Slack to Teams after a merger), updating the SyncRivo routing rule covers all New Relic alerts for that team instantly — no changes needed in New Relic itself. This decouples your monitoring configuration from your team's current messaging platform choice.
Stop configuring one notification channel per platform. One SyncRivo endpoint covers your entire messaging stack.
Ready to connect? Slack ↔ Teams connection setup →