Skip to content
Developer tools ⇄ Data warehouse

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

Keep Datadog and Exasol 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 Exasol

Close the gap between analytics and operations: Exasol holds the record while Datadog runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

Exasol is the central store where teams keep Schemas, Tables, Views, Virtual 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 Events, Dashboards, Metrics, Incidents produced in Datadog are exactly what analysts want to measure in Exasol, and the curated rows in Exasol 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 Schemas, Tables, Views, Virtual schemas in Exasol with Events, Dashboards, Metrics, Incidents 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 Sync computed metrics or customer segments from Exasol back into a CRM for sales and marketing use (reverse ETL).
  • 02 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
  • 03 Publish deploy and pipeline Events, and submit custom Metrics, into Datadog from CI/CD or a data pipeline to enrich dashboards and correlation.
  • 04 Load Events and Incidents into a warehouse to correlate deploys, alerts, and outages on one timeline for post-incident review.

Common sync patterns

Warehouse signals reach Datadog

A row scored, flagged, or enriched in Exasol 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 Events, Dashboards, Metrics, Incidents into Exasol 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 Exasol

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 Exasol objects How this pairing syncs
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. Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Events is specific to Datadog and Virtual schemas to Exasol — 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. UDF scripts In-database functions that can transform synced data after load. Dashboards is specific to Datadog and UDF scripts to Exasol — 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. Users and roles Grant read/write access for the dedicated integration account. Metrics is specific to Datadog and Users and roles to Exasol — 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. Schemas Namespaces that group the tables a sync reads from or writes into. Incidents is specific to Datadog and Schemas to Exasol — 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. Tables Primary sync target; columnar relational tables written with standard SQL. Service Level Objectives is specific to Datadog and Tables to Exasol — each maps to any object or custom field on the other side.
Hosts Infrastructure host inventory with tags and metadata from the v1 host list API; loaded into a CMDB or warehouse for asset tracking, and hosts can be muted or unmuted via the API. Views Read-only query surfaces often used as curated sources for reverse ETL. Hosts is specific to Datadog and Views to Exasol — each maps to any object or custom field on the other side.

How changes propagate between Datadog and Exasol

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 Exasol 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 Exasol as a row-level write, with types converted between the two schemas.

Exasol Datadog Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

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.
  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
What ships with Datadog ⇄ Exasol

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Datadog ⇄ Exasol 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 Exasol.

How the Datadog and Exasol 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.

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits
How it works

How to connect Datadog to Exasol — 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 Exasol 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
    Exasol connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Datadog and Exasol 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 ⇄ Exasol
    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 Exasol
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Datadog and Exasol 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 311 integrations available for Datadog and Exasol.

Popular · 6 of 311
All Datadog integrations All Exasol 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