Skip to content
Data warehouse ⇄ Developer tools

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

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

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

Dremio is the central store where teams keep Virtual datasets (views), Apache Iceberg tables, Spaces and folders, Reflections 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 Alert Policies & Conditions, NRQL Query Results, Entities, Workloads produced in Newrelic are exactly what analysts want to measure in Dremio, and the curated rows in Dremio 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 Virtual datasets (views), Apache Iceberg tables, Spaces and folders, Reflections in Dremio with Alert Policies & Conditions, NRQL Query Results, Entities, Workloads 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 Reverse-ETL aggregates computed over lake data out to CRMs and finance tools for business users.
  • 02 Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.
  • 03 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.
  • 04 Record deployment and change markers from CI/CD through NerdGraph change tracking to correlate releases with performance and error-rate shifts.

Common sync patterns

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.

Keep user and access records aligned

Where Newrelic manages users, directory, or access data, those records stay current in Dremio — and can be provisioned back from it — so ownership and permissions match across both.

Operational data lands in Dremio for analytics

Records created in Newrelic — issues, events, messages, metrics, or user changes — replicate into Dremio tables as they happen, so reporting runs on current data instead of last night's export.

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

Dremio objects Newrelic objects How this pairing syncs
Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. Synthetics Monitors Synthetic uptime and scripted browser checks managed through NerdGraph synthetics mutations (create, update, delete); monitor results are read via NRQL for availability and latency reporting. Apache Iceberg tables is specific to Dremio and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side.
Spaces and folders Namespaces that organize virtual datasets and govern access. Custom Events Custom events posted write-only to the Event API on insights-collector with a License/Ingest key; business or pipeline events pushed into New Relic to enrich dashboards, then queried back out with NRQL. Spaces and folders is specific to Dremio and Custom Events to Newrelic — each maps to any object or custom field on the other side.
Reflections Materialized accelerations that make repeated extraction queries cheaper. 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. Reflections is specific to Dremio and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side.
Jobs Query execution records useful for monitoring sync workloads. 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. Jobs is specific to Dremio and Dashboards to Newrelic — each maps to any object or custom field on the other side.
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. 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. Sources is specific to Dremio and Alert Policies & Conditions to Newrelic — each maps to any object or custom field on the other side.
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. 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. Physical datasets is specific to Dremio and NRQL Query Results to Newrelic — each maps to any object or custom field on the other side.

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

Dremio Newrelic Interval-based propagation

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

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

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

Rate-limit considerations

  • Dremio: Bounded by engine capacity and workload management rather than 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 Dremio ⇄ Newrelic

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Dremio and Newrelic connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits

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

    Choose tables

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

Dremio 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 313 integrations available for Dremio and Newrelic.

Popular · 7 of 313
All Dremio 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