Two-way sync
Changes in InterSystems IRIS or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS 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.
InterSystems IRIS 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 Views, Schemas, Persistent Classes, Globals in InterSystems IRIS with Synthetics Monitors, Custom Events, Change Tracking (Deployments), Dashboards 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.
Read and write the synced tables in InterSystems IRIS and Stacksync keeps Newrelic current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.
Updates in Newrelic arrive as row changes in InterSystems IRIS, and writes to InterSystems IRIS propagate to Newrelic within seconds, so triggers, jobs, and alerts fire without polling.
Directory and identity records in Newrelic stay matched to the users or owners table in InterSystems IRIS, so provisioning and de-provisioning flow from one source.
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.
| InterSystems IRIS objects | Newrelic objects | How this pairing syncs | |
|---|---|---|---|
| Namespaces Namespaces partition databases and determine the connection context for integrations. | 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. | Namespaces is specific to InterSystems IRIS and Alert Policies & Conditions to Newrelic — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | 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. | Stored Procedures is specific to InterSystems IRIS and NRQL Query Results to Newrelic — each maps to any object or custom field on the other side. | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | 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. | Tables is specific to InterSystems IRIS and Entities to Newrelic — each maps to any object or custom field on the other side. | |
| Views SQL views expose curated slices of data for outbound 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. | Views is specific to InterSystems IRIS and Workloads to Newrelic — each maps to any object or custom field on the other side. | |
| Schemas Schema organization scopes which tables a sync connection can see. | 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. | Schemas is specific to InterSystems IRIS and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | 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. | Persistent Classes is specific to InterSystems IRIS and Custom Events 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 InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).
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 InterSystems IRIS as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Newrelic connection.
Changes in InterSystems IRIS or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS 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 InterSystems IRIS or Newrelic record.
Track your InterSystems IRIS ⇄ Newrelic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS 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 InterSystems IRIS 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 InterSystems IRIS 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 InterSystems IRIS and Newrelic: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Namespaces and Stored Procedures), 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 InterSystems IRIS and Newrelic records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed InterSystems IRIS and Newrelic connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–Newrelic integration in-house.
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and Newrelic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. 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 InterSystems IRIS side: Views, Schemas, Persistent Classes, Globals, plus custom fields where InterSystems IRIS exposes them. On the Newrelic side: Synthetics Monitors, Custom Events, Change Tracking (Deployments), Dashboards. 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 346 integrations available for InterSystems IRIS and Newrelic.