Real-time
Two-way sync
Changes in Datadog or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Developer tools ⇄ Data warehouse
Datadog to MotherDuck integration — real-time, two-way sync
Keep Datadog and MotherDuck 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 MotherDuck
Close the gap between analytics and operations: MotherDuck holds the record while Datadog runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.
MotherDuck is the central store where teams keep Database Shares, Attached Local DuckDB Databases, Databases, Schemas for reporting and analysis; Datadog runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Hosts, Monitors, Logs, Events produced in Datadog are exactly what analysts want to measure in MotherDuck, and the curated rows in MotherDuck are what should drive the next action in Datadog. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.
Stacksync syncs Database Shares, Attached Local DuckDB Databases, Databases, Schemas in MotherDuck with Hosts, Monitors, Logs, Events in Datadog field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.
Common use cases
- 01 Share curated, synced datasets with other teams through read-only database shares
- 02 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
- 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
Warehouse signals reach Datadog
A row scored, flagged, or enriched in MotherDuck creates or updates the matching record in Datadog, so the operational tool acts on the same data the analysts already see.
Backfill history, then stay live
Load the existing set of Hosts, Monitors, Logs, Events into MotherDuck once, then keep it current with every change — you get full history plus real-time updates without a separate pipeline.
No batch jobs to babysit
New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.
What you can sync between Datadog and MotherDuck
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 | MotherDuck 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. | Database Shares Read-only copies of a database shared with other users or teams. | Logs is specific to Datadog and Database Shares to MotherDuck — 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. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | Events is specific to Datadog and Attached Local DuckDB Databases to MotherDuck — 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. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | Dashboards is specific to Datadog and Databases to MotherDuck — 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. | Schemas Namespaces within a database used to organize synced tables. | Metrics is specific to Datadog and Schemas to MotherDuck — 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. | Tables The main landing target for synced records and source for analysis. | Incidents is specific to Datadog and Tables to MotherDuck — 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. | Views Modeled projections used as outbound sync sources. | Service Level Objectives is specific to Datadog and Views to MotherDuck — each maps to any object or custom field on the other side. |
How changes propagate between Datadog and MotherDuck
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 MotherDuck 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 applied to MotherDuck as a row-level write, with types converted between the two schemas.
MotherDuck Datadog Interval-based propagation
DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
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.
- MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with Datadog ⇄ MotherDuck
Connect Datadog and MotherDuck for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Datadog–MotherDuck connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Datadog or MotherDuck 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 MotherDuck record.
Observability
Monitoring
Track your Datadog ⇄ MotherDuck 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 MotherDuck.
How the Datadog and MotherDuck 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.
MotherDuck
- Integration surface
- SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
- Authentication
- Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
- Change detection
- Polling; no log-based CDC or webhook surface is exposed
- Capabilities
- read · write
- Rate limits
- Subject to the platform's compute and concurrency limits rather than per-request API rate limits
How it works
How to connect Datadog to MotherDuck — 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.
- 01
Connect your apps
Authenticate Datadog and MotherDuck with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Datadog
connected
MotherDuck
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Datadog and MotherDuck 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.
objects · Datadog ⇄ MotherDuckCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Datadog MotherDuckCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Datadog and MotherDuck integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Datadog and MotherDuck: authenticate both systems, choose the objects to sync (such as Datadog's Logs and Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Datadog and MotherDuck connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Datadog–MotherDuck integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Datadog and MotherDuck. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Datadog: 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. On MotherDuck: Polling; no log-based CDC or webhook surface is exposed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MotherDuck side: Database Shares, Attached Local DuckDB Databases, Databases, Schemas, plus custom fields where MotherDuck exposes them. On the Datadog side: Hosts, Monitors, Logs, Events. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 328 integrations available for Datadog and MotherDuck.
Popular · 7 of 328
-
Datadog ⇄ Dremio -
Datadog ⇄ Exasol -
Datadog ⇄ Firebolt -
Datadog ⇄ Google Cloud Platform -
MotherDuck ⇄ Jms -
MotherDuck ⇄ Newrelic -
MotherDuck ⇄ Opsgenie
No integrations match .
