Two-way sync
Changes in Exasol or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol 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.
Exasol is the central store where teams keep Users and roles, Schemas, Tables, Views 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 Exasol, and the curated rows in Exasol 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 Users and roles, Schemas, Tables, Views in Exasol 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.
A row scored, flagged, or enriched in Exasol creates or updates the matching record in Newrelic, so the operational tool acts on the same data the analysts already see.
Load the existing set of Custom Events, Change Tracking (Deployments), Dashboards, Alert Policies & Conditions into Exasol once, then keep it current with every change — you get full history plus real-time updates without a separate pipeline.
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.
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.
| Exasol objects | Newrelic objects | How this pairing syncs | |
|---|---|---|---|
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | 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. | Virtual schemas is specific to Exasol and Workloads to Newrelic — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | 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. | UDF scripts is specific to Exasol and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side. | |
| Users and roles Grant read/write access for the dedicated integration account. | 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. | Users and roles is specific to Exasol and Custom Events to Newrelic — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | 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. | Schemas is specific to Exasol and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | 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 is specific to Exasol and Dashboards to Newrelic — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | 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 is specific to Exasol 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.
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
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 Exasol as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Newrelic connection.
Changes in Exasol or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol 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 Exasol or Newrelic record.
Track your Exasol ⇄ Newrelic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol 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 Exasol 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 Exasol 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 Exasol and Newrelic: authenticate both systems, choose the objects to sync (such as Exasol's Virtual schemas and UDF scripts), map fields visually, and changes propagate both ways in milliseconds — no code required.
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). 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.
Exasol: Bulk loading uses the IMPORT statement, which is more efficient than row-by-row inserts for sync workloads. 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 Exasol and Newrelic 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 Exasol and Newrelic records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Exasol and Newrelic connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Exasol–Newrelic integration in-house.
Yes — Stacksync ships production-grade connectors for both Exasol and Newrelic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 311 integrations available for Exasol and Newrelic.