Skip to content
Database ⇄ Developer tools

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

Keep DuckDB 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 DuckDB and Newrelic

Keep DuckDB and Newrelic in step: the rows in your database and the Change Tracking (Deployments), Dashboards, Alert Policies & Conditions, NRQL Query Results your engineering tools track stay consistent in real time, in both directions.

DuckDB is where your application's durable data lives; Newrelic is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs Database files, Schemas, Tables, Views in DuckDB with Change Tracking (Deployments), Dashboards, Alert Policies & Conditions, NRQL Query Results in Newrelic field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
  • 02 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
  • 03 Provision and update Dashboards and Alert Policies from a config repository or database through NerdGraph so definitions stay versioned and consistent across accounts and environments.
  • 04 Push custom business or pipeline Events and Metrics into New Relic through the Event and Metric APIs so they appear alongside APM data in dashboards and NRQL.

Common sync patterns

One integration pattern instead of per-tool API code

Read and write the synced tables in DuckDB and Stacksync keeps Newrelic current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.

React to changes on either side in near real time

Updates in Newrelic arrive as row changes in DuckDB, and writes to DuckDB propagate to Newrelic within seconds, so triggers, jobs, and alerts fire without polling.

Where Newrelic manages users or groups: keep identity aligned

Directory and identity records in Newrelic stay matched to the users or owners table in DuckDB, so provisioning and de-provisioning flow from one source.

What you can sync between DuckDB 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.

DuckDB objects Newrelic objects How this pairing syncs
Views SQL views used to shape or filter data for downstream consumers. 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. Views is specific to DuckDB and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side.
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. 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. External files (Parquet/CSV/JSON) is specific to DuckDB and Dashboards to Newrelic — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. 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. Attached databases is specific to DuckDB and Alert Policies & Conditions to Newrelic — each maps to any object or custom field on the other side.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. 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 files is specific to DuckDB and NRQL Query Results to Newrelic — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. 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. Schemas is specific to DuckDB and Entities to Newrelic — each maps to any object or custom field on the other side.
Tables Columnar tables created via SQL; the destination for materialized sync data. 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. Tables is specific to DuckDB and Workloads to Newrelic — each maps to any object or custom field on the other side.

How changes propagate between DuckDB 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.

DuckDB Newrelic Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

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

Newrelic DuckDB 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 DuckDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • 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 DuckDB ⇄ Newrelic

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever DuckDB 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 DuckDB or Newrelic record.

Observability

Monitoring

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

Trading partners

EDI

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

How the DuckDB and Newrelic connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

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 DuckDB 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 DuckDB 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
    DuckDB connected
    Newrelic connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DuckDB 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 · DuckDB ⇄ 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
    DuckDB Newrelic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DuckDB 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 327 integrations available for DuckDB and Newrelic.

Popular · 8 of 327
All DuckDB 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