Two-way sync
Changes in BigQuery or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery 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.
BigQuery is the central store where teams keep Tables, Partitioned tables, Clustered tables, Datasets 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 Custom Events, Change Tracking (Deployments), Dashboards, Alert Policies & Conditions produced in Newrelic are exactly what analysts want to measure in BigQuery, and the curated rows in BigQuery 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 Tables, Partitioned tables, Clustered tables, Datasets in BigQuery with Custom Events, Change Tracking (Deployments), Dashboards, Alert Policies & Conditions 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.
Where Newrelic manages users, directory, or access data, those records stay current in BigQuery — and can be provisioned back from it — so ownership and permissions match across both.
Records created in Newrelic — issues, events, messages, metrics, or user changes — replicate into BigQuery tables as they happen, so reporting runs on current data instead of last night's export.
A row scored, flagged, or enriched in BigQuery creates or updates the matching record in Newrelic, so the operational tool acts on the same data the analysts already see.
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.
| BigQuery objects | Newrelic objects | How this pairing syncs | |
|---|---|---|---|
| Datasets Organizational container — you pick which dataset’s tables to sync. | 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. | Datasets is specific to BigQuery and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side. | |
| Projects Connection scope: the service account grants access per project. | 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. | Projects is specific to BigQuery and Custom Events to Newrelic — each maps to any object or custom field on the other side. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | 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. | Tables is specific to BigQuery and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | 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. | Partitioned tables is specific to BigQuery and Dashboards to Newrelic — each maps to any object or custom field on the other side. | |
| Clustered tables Supported; clustering is transparent to the sync. | 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. | Clustered tables is specific to BigQuery and Alert Policies & Conditions to Newrelic — each maps to any object or custom field on the other side. |
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.
DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").
DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.
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 BigQuery as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Newrelic connection.
Changes in BigQuery or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or Newrelic data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BigQuery or Newrelic record.
Track your BigQuery ⇄ Newrelic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and Newrelic.
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.
Authenticate BigQuery 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.
Pick the BigQuery 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between BigQuery and Newrelic: authenticate both systems, choose the objects to sync (such as BigQuery's Datasets and Projects), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the BigQuery side: Tables, Partitioned tables, Clustered tables, Datasets, plus custom fields where BigQuery exposes them. On the Newrelic side: Custom Events, Change Tracking (Deployments), Dashboards, Alert Policies & Conditions. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for BigQuery and Newrelic: Keep user and access records aligned; Operational data lands in BigQuery for analytics; Warehouse signals reach Newrelic. Where Newrelic manages users, directory, or access data, those records stay current in BigQuery — and can be provisioned back from it — so ownership and permissions match across both.
BigQuery: GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs. Authentication: Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver. Newrelic: 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). Stacksync manages authentication, retries, and rate limits on both sides.
BigQuery: BigQuery is serverless: there are no clusters or warehouses to size, and storage and compute are billed separately. Newrelic: NerdGraph supports mutations for dashboards, alert policies and conditions, workloads, tags, synthetics, and change tracking, so the connector writes configuration into New Relic as well as reading it. Stacksync's field mapping accounts for these differences between BigQuery and Newrelic without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 421 integrations available for BigQuery and Newrelic.