Real-time
Two-way sync
Changes in Exasol or Splunk instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Analytics
Exasol to Splunk integration — real-time, two-way sync
Keep Exasol and Splunk 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 Exasol and Splunk
Put the same events, users, and metrics on both sides: Splunk and Exasol stay current in real time, in both directions.
Splunk is where teams explore, visualize, and report; Exasol is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.
Stacksync syncs KV Store Collections, Indexes, HTTP Event Collector, Users and Roles in Splunk with Tables, Views, Virtual schemas, UDF scripts in Exasol field by field, in real time, and in both directions. You decide which system owns which fields, and Stacksync resolves conflicts by rules you set. Whether the flow is warehouse tables feeding live reports or captured events and segments landing back in Exasol, every copy stays consistent.
Common use cases
- 01 Ingest application, CRM, or database records into Splunk via the HTTP Event Collector so operational data lands alongside logs for correlation and dashboards.
- 02 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
- 03 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
- 04 Keep dimension tables such as customers and products aligned with the systems of record.
Common sync patterns
Where Splunk produces segments or scores: results back to the warehouse
Cohorts, segments, and computed metrics defined in Splunk write to Exasol as tables the rest of the stack can query and join.
Shared user and account keys
Users and accounts tracked in Splunk line up with the customer or user rows in Exasol on a stable key, so both sides count the same population.
Corrections propagate instead of reloading
When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.
What you can sync between Exasol and Splunk
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.
| Exasol objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Users and roles Grant read/write access for the dedicated integration account. | Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking. | Virtual schemas is specific to Exasol and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation. | UDF scripts is specific to Exasol and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Schemas is specific to Exasol and Dashboards to Splunk — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Tables is specific to Exasol and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Views is specific to Exasol and Saved Searches to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Exasol and Splunk
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.
Exasol Splunk 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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Exasol Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Exasol ⇄ Splunk
Connect Exasol and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Exasol or Splunk 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 Exasol or Splunk record.
Observability
Monitoring
Track your Exasol ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Exasol and Splunk.
How the Exasol and Splunk connectors work
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
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Exasol to Splunk — 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 Exasol and Splunk with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Exasol
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Exasol and Splunk 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 · Exasol ⇄ SplunkCustomers 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.
Exasol SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Exasol and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and Splunk: authenticate both systems, choose the objects to sync (such as Exasol's Users and roles and Virtual schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). Splunk: REST API (management API + HTTP Event Collector). Authentication: HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud). Stacksync manages authentication, retries, and rate limits on both sides.
-
Splunk: Searches are asynchronous: POST /services/search/jobs returns a search ID (SID), and results are fetched from /services/search/jobs/{sid}/results once the job completes; oneshot and export modes return results synchronously. Exasol: Exasol is an in-memory, columnar MPP database that creates and maintains indexes automatically based on query patterns, rather than requiring manual index design. Stacksync's field mapping accounts for these differences between Exasol and Splunk 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 Exasol and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Exasol and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Exasol–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Exasol and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 404 integrations available for Exasol and Splunk.
Popular · 8 of 404
-
Exasol ⇄ Mixpanel -
Exasol ⇄ Microsoft Power Bi -
Exasol ⇄ Tableau -
Exasol ⇄ Adobeanalytics -
Splunk ⇄ IBM Netezza -
Splunk ⇄ Materialize -
Splunk ⇄ Rockset -
Splunk ⇄ Starburst Enterprise
No integrations match .
