Skip to content
Developer tools ⇄ Database

Newrelic to OCI Database (Oracle Cloud) integration — real-time, two-way sync

Keep Newrelic and OCI Database (Oracle Cloud) in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Newrelic and OCI Database (Oracle Cloud)

Keep OCI Database (Oracle Cloud) and Newrelic in step: the rows in your database and the Synthetics Monitors, Custom Events, Change Tracking (Deployments), Dashboards your engineering tools track stay consistent in real time, in both directions.

OCI Database (Oracle Cloud) 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, Materialized views, Schemas in OCI Database (Oracle Cloud) 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.

Common use cases

  • 01 Replicate operational tables from OCI to an analytics warehouse with log-based CDC instead of nightly batch dumps.
  • 02 Run on-prem Oracle and OCI side by side during a cloud migration while keeping both ends writable.
  • 03 Sync the Entity catalog into a CMDB or warehouse for asset inventory, and add or replace entity Tags to keep ownership and environment metadata current.
  • 04 Provision Synthetics Monitors from a service catalog and read their results via NRQL for availability and latency reporting in SQL.

Common sync patterns

Where Newrelic manages users or groups: keep identity aligned

Directory and identity records in Newrelic stay matched to the users or owners table in OCI Database (Oracle Cloud), so provisioning and de-provisioning flow from one source.

Turn rows into the records your tools track

A new or changed row in OCI Database (Oracle Cloud) 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.

Land tool activity as queryable rows

Records and events from Newrelic arrive in OCI Database (Oracle Cloud) as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

What you can sync between Newrelic and OCI Database (Oracle Cloud)

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 OCI Database (Oracle Cloud) 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. Sequences Key generators that matter when writing new rows from external systems Alert Policies & Conditions is specific to Newrelic and Sequences to OCI Database (Oracle Cloud) — 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. PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place NRQL Query Results is specific to Newrelic and PL/SQL procedures and packages to OCI Database (Oracle Cloud) — 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. JSON collections Document-style storage in the converged engine, synced alongside relational tables Entities is specific to Newrelic and JSON collections to OCI Database (Oracle Cloud) — 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. Partitions Physical table subdivisions relevant when replicating large fact tables Workloads is specific to Newrelic and Partitions to OCI Database (Oracle Cloud) — 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. Tables The primary sync surface; rows are read and written directly over SQL Synthetics Monitors is specific to Newrelic and Tables to OCI Database (Oracle Cloud) — 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. Views Read-only projections used to expose curated subsets to downstream systems Custom Events is specific to Newrelic and Views to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.

How changes propagate between Newrelic and OCI Database (Oracle Cloud)

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.

Newrelic OCI Database (Oracle Cloud) Sub-second propagation

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 OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.

OCI Database (Oracle Cloud) Newrelic Sub-second propagation

DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.

DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Newrelic: NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
  • OCI Database (Oracle Cloud): Throughput bounded by instance sizing rather than API quotas.
What ships with Newrelic ⇄ OCI Database (Oracle Cloud)

Connect Newrelic and OCI Database (Oracle Cloud) for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Newrelic–OCI Database (Oracle Cloud) connection.

Real-time

Two-way sync

Changes in Newrelic or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Newrelic or OCI Database (Oracle Cloud) data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Newrelic or OCI Database (Oracle Cloud) record.

Observability

Monitoring

Track your Newrelic ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Newrelic and OCI Database (Oracle Cloud).

How the Newrelic and OCI Database (Oracle Cloud) connectors work

Newrelic

Integration surface
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).
Change detection
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.
Capabilities
read · write · webhooks
Rate limits
NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.

OCI Database (Oracle Cloud)

Integration surface
SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP
Authentication
database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available
Change detection
log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling
Capabilities
read · write · CDC
Rate limits
throughput bounded by instance sizing rather than API quotas
How it works

How to connect Newrelic to OCI Database (Oracle Cloud) — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Newrelic and OCI Database (Oracle Cloud) with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Newrelic connected
    OCI Database (Oracle Cloud) connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Newrelic and OCI Database (Oracle Cloud) 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Newrelic ⇄ OCI Database (Oracle Cloud)
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Newrelic OCI Database (Oracle Cloud)
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Newrelic and OCI Database (Oracle Cloud) integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.