Skip to content
Data warehouse ⇄ Developer tools

MotherDuck to Newrelic integration — real-time, two-way sync

Keep MotherDuck and Newrelic in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect MotherDuck and Newrelic

Close the gap between analytics and operations: MotherDuck holds the record while Newrelic runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

MotherDuck is the central store where teams keep Views, Database Shares, Attached Local DuckDB Databases, Databases for reporting and analysis; Newrelic runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) produced in Newrelic are exactly what analysts want to measure in MotherDuck, and the curated rows in MotherDuck are what should drive the next action in Newrelic. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Views, Database Shares, Attached Local DuckDB Databases, Databases in MotherDuck with Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) in Newrelic field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Sync modeled MotherDuck tables outward to operational tools for activation
  • 02 Share curated, synced datasets with other teams through read-only database shares
  • 03 Record deployment and change markers from CI/CD through NerdGraph change tracking to correlate releases with performance and error-rate shifts.
  • 04 Sync the Entity catalog into a CMDB or warehouse for asset inventory, and add or replace entity Tags to keep ownership and environment metadata current.

Common sync patterns

Backfill history, then stay live

Load the existing set of Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) into MotherDuck once, then keep it current with every change — you get full history plus real-time updates without a separate pipeline.

No batch jobs to babysit

New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.

One shared record, kept consistent

Where both systems track the same entity, a change on either side propagates to the other, ending the manual reconciliation between the operational copy and the warehouse copy.

What you can sync between MotherDuck and Newrelic

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

MotherDuck objects Newrelic objects How this pairing syncs
Schemas Namespaces within a database used to organize synced tables. Change Tracking (Deployments) Deployment and change markers recorded through NerdGraph changeTrackingCreateDeployment; written from CI/CD to annotate charts, and read back via NRQL on the Deployment event for release correlation. Schemas is specific to MotherDuck and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side.
Tables The main landing target for synced records and source for analysis. Dashboards Dashboard definitions and widgets via NerdGraph dashboardCreate/dashboardUpdate/dashboardDelete mutations and entity queries, with full CRUD; exported for backup and audit or provisioned and updated programmatically from a source of truth. Tables is specific to MotherDuck and Dashboards to Newrelic — each maps to any object or custom field on the other side.
Views Modeled projections used as outbound sync sources. Alert Policies & Conditions Alert policies and NRQL alert conditions managed through NerdGraph alertsPolicy and alertsNrqlCondition mutations with full create, update, and delete; read out for audit or provisioned from a config source so alerting stays consistent across accounts. Views is specific to MotherDuck and Alert Policies & Conditions to Newrelic — each maps to any object or custom field on the other side.
Database Shares Read-only copies of a database shared with other users or teams. NRQL Query Results Telemetry events, metrics, logs, and spans queried through NerdGraph's nrql field (or the legacy Insights query API) over time windows; read-only and bounded by data retention, commonly streamed into a warehouse for long-term analysis. Database Shares is specific to MotherDuck and NRQL Query Results to Newrelic — each maps to any object or custom field on the other side.
Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Entities The entity catalog of APM applications, hosts, services, and monitors searched via NerdGraph entitySearch; read for inventory, with tags added or replaced through taggingAddTagsToEntity so ownership and environment metadata stay in sync. Attached Local DuckDB Databases is specific to MotherDuck and Entities to Newrelic — each maps to any object or custom field on the other side.
Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Workloads Workload groupings of related entities via NerdGraph workloadCreate/workloadUpdate/workloadDelete with full CRUD; read for status rollups or provisioned from a service catalog to keep team-level views current. Databases is specific to MotherDuck and Workloads to Newrelic — each maps to any object or custom field on the other side.

How changes propagate between MotherDuck and Newrelic

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

MotherDuck Newrelic Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.

Newrelic MotherDuck Sub-second propagation

DetectionNewrelic notifies Stacksync of record changes through webhook events. NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans).

DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
  • Newrelic: NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
What ships with MotherDuck ⇄ Newrelic

Connect MotherDuck and Newrelic for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–Newrelic connection.

Real-time

Two-way sync

Changes in MotherDuck or Newrelic instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MotherDuck or Newrelic data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single MotherDuck or Newrelic record.

Observability

Monitoring

Track your MotherDuck ⇄ Newrelic sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MotherDuck and Newrelic.

How the MotherDuck and Newrelic connectors work

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide

Newrelic

Integration surface
NerdGraph (GraphQL) plus REST data-ingest APIs (Event, Metric, Log, Trace) and the legacy REST API v2
Authentication
User API key (prefixed NRAK-) sent in the API-Key header for NerdGraph queries and mutations; the data-ingest APIs (Event, Metric, Log) use a License/Ingest key in the Api-Key header. Keys, endpoints, and data are region-scoped (US, EU, JP).
Change detection
NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans); config objects such as dashboards, alert policies, and workloads carry no modified-date and are diffed on each run. Alert workflows can push outbound webhook notifications for near-real-time alerting. No CDC feed.
Capabilities
read · write · webhooks
Rate limits
NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
How it works

How to connect MotherDuck to Newrelic — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate MotherDuck and Newrelic with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    MotherDuck connected
    Newrelic connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MotherDuck and Newrelic objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · MotherDuck ⇄ Newrelic
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    MotherDuck Newrelic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MotherDuck and Newrelic integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 328 integrations available for MotherDuck and Newrelic.

Popular · 8 of 328
All MotherDuck integrations All Newrelic integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own