Two-way sync
Changes in MySQL or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Keep MySQL 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.
MySQL is where your application's durable data lives; Newrelic is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.
Stacksync syncs Tables, Views, Columns, Primary and Unique Keys in MySQL with Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) in Newrelic field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.
Directory and identity records in Newrelic stay matched to the users or owners table in MySQL, so provisioning and de-provisioning flow from one source.
A new or changed row in MySQL creates or updates the matching record in Newrelic, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.
Records and events from Newrelic arrive in MySQL as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.
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.
| MySQL objects | Newrelic objects | How this pairing syncs | |
|---|---|---|---|
| Tables The primary sync target; rows map to records in connected systems. | 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 is specific to MySQL and Workloads to Newrelic — each maps to any object or custom field on the other side. | |
| Views Read-side projections used as outbound sync sources. | 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 is specific to MySQL and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets with engine-typed values. | 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. | Columns is specific to MySQL and Custom Events to Newrelic — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | 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. | Primary and Unique Keys is specific to MySQL and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side. | |
| JSON Columns Validated semi-structured payloads for nested SaaS data. | 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. | JSON Columns is specific to MySQL and Dashboards to Newrelic — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic that can post-process synced rows. | 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. | Stored Procedures is specific to MySQL 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 MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
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 MySQL as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Newrelic connection.
Changes in MySQL or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MySQL 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 MySQL or Newrelic record.
Track your MySQL ⇄ Newrelic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MySQL 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 MySQL 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 MySQL 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 MySQL and Newrelic: authenticate both systems, choose the objects to sync (such as MySQL's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 MySQL and Newrelic records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MySQL and Newrelic connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MySQL–Newrelic integration in-house.
Yes — Stacksync ships production-grade connectors for both MySQL and Newrelic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). On Newrelic: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MySQL side: Tables, Views, Columns, Primary and Unique Keys, plus custom fields where MySQL exposes them. On the Newrelic side: Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments). Stacksync auto-detects both schemas and converts types between the two systems.
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 425 integrations available for MySQL and Newrelic.