Two-way sync
Changes in Newrelic or OpenSearch instantly reflect in both systems. No stale data, no manual imports.
Keep Newrelic and OpenSearch in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
OpenSearch 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 Documents, Index aliases, Index templates, Ingest pipelines in OpenSearch 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 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 OpenSearch 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 OpenSearch, and writes to OpenSearch 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 OpenSearch, 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.
| Newrelic objects | OpenSearch objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Snapshots Backup artifacts, relevant when reseeding an index from a repository | Alert Policies & Conditions is specific to Newrelic and Snapshots to OpenSearch — 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. | Indexes The core container; synced records land in indexes with defined mappings | NRQL Query Results is specific to Newrelic and Indexes to OpenSearch — 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. | Documents JSON records written via the index and bulk APIs and read via search queries | Entities is specific to Newrelic and Documents to OpenSearch — 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. | Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills | Workloads is specific to Newrelic and Index aliases to OpenSearch — 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. | Index templates Mapping and settings presets applied to new indexes a sync creates | Synthetics Monitors is specific to Newrelic and Index templates to OpenSearch — each maps to any object or custom field on the other side. | |
| 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. | Ingest pipelines Server-side processors that transform documents as they are written | Custom Events is specific to Newrelic and Ingest pipelines to OpenSearch — 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 written to OpenSearch through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls OpenSearch for changes on an incremental schedule, reading only records changed since the previous pass. No native change feed.
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–OpenSearch connection.
Changes in Newrelic or OpenSearch instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Newrelic or OpenSearch 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 OpenSearch record.
Track your Newrelic ⇄ OpenSearch sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Newrelic and OpenSearch.
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 OpenSearch 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 OpenSearch 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 OpenSearch: authenticate both systems, choose the objects to sync (such as Newrelic's Alert Policies & Conditions and NRQL Query Results), map fields visually, and changes propagate both ways in milliseconds — no code required.
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). OpenSearch: REST API over HTTP(S) with JSON payloads. Authentication: Basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service. Stacksync manages authentication, retries, and rate limits on both sides.
OpenSearch: Amazon OpenSearch Service domains typically authenticate with IAM request signing, while self-managed clusters use the security plugin's basic auth or certificates. 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 Newrelic and OpenSearch 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 OpenSearch records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Newrelic and OpenSearch connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Newrelic–OpenSearch integration in-house.
Yes — Stacksync ships production-grade connectors for both Newrelic and OpenSearch. 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 303 integrations available for Newrelic and OpenSearch.