Skip to content
Developer tools ⇄ Database

Datadog to OpenSearch integration — real-time, two-way sync

Keep Datadog 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.

  • 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 Datadog and OpenSearch

Keep OpenSearch and Datadog in step: the rows in your database and the Incidents, Service Level Objectives, Hosts, Monitors your engineering tools track stay consistent in real time, in both directions.

OpenSearch is where your application's durable data lives; Datadog 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 Index aliases, Index templates, Ingest pipelines, Data streams in OpenSearch with Incidents, Service Level Objectives, Hosts, Monitors in Datadog 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 Sync product catalogs from an ERP or database into the indexes that back storefront search.
  • 02 Keep Postgres as the source of truth while mirroring rows to OpenSearch for full-text and vector queries.
  • 03 Sync Monitors and their alert state into Postgres so reliability teams query alert history and noisy-monitor trends in SQL.
  • 04 Provision and update Datadog Monitors from a config database or Git so alert definitions stay consistent across teams and environments.

Common sync patterns

React to changes on either side in near real time

Updates in Datadog arrive as row changes in OpenSearch, and writes to OpenSearch propagate to Datadog within seconds, so triggers, jobs, and alerts fire without polling.

Where Datadog manages users or groups: keep identity aligned

Directory and identity records in Datadog stay matched to the users or owners table in OpenSearch, so provisioning and de-provisioning flow from one source.

Turn rows into the records your tools track

A new or changed row in OpenSearch creates or updates the matching record in Datadog, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.

What you can sync between Datadog and OpenSearch

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.

Datadog objects OpenSearch objects How this pairing syncs
Logs Log events searched via the v2 Logs search endpoint by time window and submittable through the log intake API; commonly streamed to a warehouse for retention beyond Datadog's storage period. Data streams Append-oriented time-series storage for logs and events pushed from source systems Logs is specific to Datadog and Data streams to OpenSearch — each maps to any object or custom field on the other side.
Events The event stream (deploys, alerts, comments) searched via the v2 Events endpoint and posted via POST /api/v1/events; used to correlate deploy and incident timelines or to publish deploy and pipeline events into Datadog. Snapshots Backup artifacts, relevant when reseeding an index from a repository Events is specific to Datadog and Snapshots to OpenSearch — each maps to any object or custom field on the other side.
Dashboards Dashboard definitions and widgets via the v1 Dashboards API with full CRUD; exported for backup and audit, or created and updated programmatically from a source of truth. Indexes The core container; synced records land in indexes with defined mappings Dashboards is specific to Datadog and Indexes to OpenSearch — each maps to any object or custom field on the other side.
Metrics Time-series metrics queried in aggregate windows through the query API and submitted via POST /api/v1/series; individual raw points cannot be extracted beyond retention. Documents JSON records written via the index and bulk APIs and read via search queries Metrics is specific to Datadog and Documents to OpenSearch — each maps to any object or custom field on the other side.
Incidents Incident records from the v2 Incidents API with full CRUD, including status and timeline fields; landed in a database for MTTR reporting or created and updated from an external incident workflow. Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills Incidents is specific to Datadog and Index aliases to OpenSearch — each maps to any object or custom field on the other side.
Service Level Objectives SLO definitions and status history via the v1 SLO API with full CRUD; read out for reliability and error-budget reporting, or provisioned and updated from a reliability config. Index templates Mapping and settings presets applied to new indexes a sync creates Service Level Objectives is specific to Datadog and Index templates to OpenSearch — each maps to any object or custom field on the other side.

How changes propagate between Datadog and OpenSearch

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.

Datadog OpenSearch Sub-second propagation

DetectionDatadog notifies Stacksync of record changes through webhook events. Polling with time-windowed search queries on Logs and Events (timestamp cursor).

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

OpenSearch Datadog Interval-based propagation

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 Datadog through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Datadog: Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.
  • OpenSearch: Throughput bounded by cluster sizing rather than fixed API quotas.
What ships with Datadog ⇄ OpenSearch

Connect Datadog and OpenSearch for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Datadog–OpenSearch connection.

Real-time

Two-way sync

Changes in Datadog or OpenSearch instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Datadog or OpenSearch 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 Datadog or OpenSearch record.

Observability

Monitoring

Track your Datadog ⇄ OpenSearch sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Datadog and OpenSearch.

How the Datadog and OpenSearch connectors work

Datadog

Integration surface
REST API (v1 and v2)
Authentication
API key (DD-API-KEY) plus an Application key (DD-APPLICATION-KEY) sent as request headers; application keys are tied to the creating user and inherit that user's permissions and authorization scopes.
Change detection
Polling with time-windowed search queries on Logs and Events (timestamp cursor); monitor alerts can also push via the Webhooks notification integration. No modified-date CDC on mutable objects.
Capabilities
read · write · webhooks
Rate limits
Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.

OpenSearch

Integration surface
REST API over HTTP(S) with JSON payloads
Authentication
basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service
Change detection
no native change feed; reads rely on queries with scroll or point-in-time polling
Capabilities
read · write
Rate limits
throughput bounded by cluster sizing rather than fixed API quotas
How it works

How to connect Datadog to OpenSearch — 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 Datadog 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Datadog connected
    OpenSearch connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Datadog 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Datadog ⇄ OpenSearch
    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
    Datadog OpenSearch
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Datadog and OpenSearch 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 303 integrations available for Datadog and OpenSearch.

Popular · 7 of 303
All Datadog integrations All OpenSearch integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own