Skip to content
Developer tools ⇄ Data warehouse

Newrelic to Starburst Enterprise integration — real-time, two-way sync

Keep Newrelic and Starburst Enterprise 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 Newrelic and Starburst Enterprise

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

Starburst Enterprise is the central store where teams keep Columns, Catalogs, Schemas, Tables 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 Dashboards, Alert Policies & Conditions, NRQL Query Results, Entities produced in Newrelic are exactly what analysts want to measure in Starburst Enterprise, and the curated rows in Starburst Enterprise 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 Columns, Catalogs, Schemas, Tables in Starburst Enterprise with Dashboards, Alert Policies & Conditions, NRQL Query Results, Entities 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 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
  • 02 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • 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

Backfill history, then stay live

Load the existing set of Dashboards, Alert Policies & Conditions, NRQL Query Results, Entities into Starburst Enterprise 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 Newrelic and Starburst Enterprise

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.

Newrelic objects Starburst Enterprise objects How this pairing syncs
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 Queryable relations; writes pass through to sources whose connectors support them. Workloads is specific to Newrelic and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Views Engine-level SQL views used to shape federated data before syncing it out. Synthetics Monitors is specific to Newrelic and Views to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Materialized views Precomputed results that make repeated sync reads cheaper. Custom Events is specific to Newrelic and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Columns Typed per the Trino type system, mapped from each source's native types. Change Tracking (Deployments) is specific to Newrelic and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Dashboards is specific to Newrelic and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Alert Policies & Conditions is specific to Newrelic and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Newrelic and Starburst Enterprise

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.

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

Starburst Enterprise Newrelic Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

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

Rate-limit considerations

  • 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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Newrelic ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Newrelic and Starburst Enterprise connectors work

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.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Newrelic to Starburst Enterprise — 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 Newrelic and Starburst Enterprise 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
    Newrelic connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Newrelic and Starburst Enterprise 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 315 integrations available for Newrelic and Starburst Enterprise.

Popular · 7 of 315
All Newrelic integrations All Starburst Enterprise 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