Two-way sync
Changes in Newrelic or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Keep Newrelic and Snowflake in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Snowflake is the central store where teams keep Virtual Warehouses, Databases, 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 NRQL Query Results, Entities, Workloads, Synthetics Monitors produced in Newrelic are exactly what analysts want to measure in Snowflake, and the curated rows in Snowflake 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 Warehouses, Databases, Schemas, Tables in Snowflake with NRQL Query Results, Entities, Workloads, Synthetics Monitors 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 Snowflake — 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 Snowflake tables as they happen, so reporting runs on current data instead of last night's export.
A row scored, flagged, or enriched in Snowflake 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.
| Newrelic objects | Snowflake objects | How this pairing syncs | |
|---|---|---|---|
| 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 The main landing and activation target for synced records. | Dashboards is specific to Newrelic and Tables to Snowflake — 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. | Views Modeled projections used as the source side of outbound syncs. | Alert Policies & Conditions is specific to Newrelic and Views to Snowflake — each maps to any object or custom field on the other side. | |
| 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. | Materialized Views Precomputed results synced outward for low-latency reads. | NRQL Query Results is specific to Newrelic and Materialized Views to Snowflake — each maps to any object or custom field on the other side. | |
| 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. | Streams Row-level change records on a table, consumed to process deltas instead of full scans. | Entities is specific to Newrelic and Streams to Snowflake — each maps to any object or custom field on the other side. | |
| 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. | Stages File staging areas used for bulk loads into synced tables. | Workloads is specific to Newrelic and Stages to Snowflake — 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. | Tasks Scheduled SQL used to transform synced data after it lands. | Synthetics Monitors is specific to Newrelic and Tasks to Snowflake — 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.
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 Snowflake as a row-level write, with types converted between the two schemas.
DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.
DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Newrelic–Snowflake connection.
Changes in Newrelic or Snowflake instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Newrelic or Snowflake data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Newrelic or Snowflake record.
Track your Newrelic ⇄ Snowflake sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Newrelic and Snowflake.
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 Newrelic and Snowflake 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 Newrelic and Snowflake 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 Newrelic and Snowflake: authenticate both systems, choose the objects to sync (such as Newrelic's Dashboards and Alert Policies & Conditions), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Newrelic and Snowflake: Keep user and access records aligned; Operational data lands in Snowflake for analytics; Warehouse signals reach Newrelic. Where Newrelic manages users, directory, or access data, those records stay current in Snowflake — and can be provisioned back from it — so ownership and permissions match across both.
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). Snowflake: SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API. Authentication: Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles. Stacksync manages authentication, retries, and rate limits on both sides.
Snowflake: Views (materialized and non-materialized) are not yet supported (coming soon). Newrelic: Telemetry (events, metrics, logs, spans) is time-series queried by NRQL over timestamp windows and bounded by data retention, so it has no modified-date and raw points cannot be pulled beyond the retention period. Stacksync's field mapping accounts for these differences between Newrelic and Snowflake without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Newrelic and Snowflake records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Newrelic and Snowflake connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Newrelic–Snowflake integration in-house.
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 426 integrations available for Newrelic and Snowflake.