Real-time
Two-way sync
Changes in Dremio or Splunk instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Analytics
Dremio to Splunk integration — real-time, two-way sync
Keep Dremio 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 Dremio and Splunk
Put the same events, users, and metrics on both sides: Splunk and Dremio stay current in real time, in both directions.
Splunk is where teams explore, visualize, and report; Dremio 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 Dashboards, Search Results, Saved Searches, Fired Alerts in Splunk with Apache Iceberg tables, Spaces and folders, Reflections, Jobs in Dremio 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 Dremio, every copy stays consistent.
Common use cases
- 01 Sync fired-alert history and saved-search definitions into Postgres so security and reliability teams query alert trends and detection coverage in SQL.
- 02 Ingest application, CRM, or database records into Splunk via the HTTP Event Collector so operational data lands alongside logs for correlation and dashboards.
- 03 Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.
- 04 Sync curated Dremio views into an operational Postgres so applications get low-latency access to lakehouse data.
Common sync patterns
Where Dremio holds the source tables: live data in the reporting layer
Records maintained in Dremio flow into Splunk as they change, so dashboards and reports read current rows rather than an overnight extract.
Where Splunk produces segments or scores: results back to the warehouse
Cohorts, segments, and computed metrics defined in Splunk write to Dremio 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 Dremio on a stable key, so both sides count the same population.
What you can sync between Dremio 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.
| Dremio objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Spaces and folders Namespaces that organize virtual datasets and govern access. | 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. | Spaces and folders is specific to Dremio and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Reflections Materialized accelerations that make repeated extraction queries cheaper. | 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. | Reflections is specific to Dremio and Saved Searches to Splunk — each maps to any object or custom field on the other side. | |
| Jobs Query execution records useful for monitoring sync workloads. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Jobs is specific to Dremio and Fired Alerts to Splunk — each maps to any object or custom field on the other side. | |
| Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. | KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in. | Sources is specific to Dremio and KV Store Collections to Splunk — each maps to any object or custom field on the other side. | |
| Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. | 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. | Physical datasets is specific to Dremio and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. | 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. | Virtual datasets (views) is specific to Dremio and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Dremio 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.
Dremio Splunk Interval-based propagation
DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Dremio 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 Dremio as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Dremio: Bounded by engine capacity and workload management rather than API rate 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 Dremio ⇄ Splunk
Connect Dremio and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dremio 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 Dremio or Splunk record.
Observability
Monitoring
Track your Dremio ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dremio and Splunk.
How the Dremio and Splunk connectors work
Dremio
- Integration surface
- Arrow Flight SQL, JDBC/ODBC, and a REST API
- Authentication
- Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
- Change detection
- Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
- Capabilities
- read · write
- Rate limits
- Bounded by engine capacity and workload management rather than API rate 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 Dremio 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 Dremio 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.
Dremio
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dremio 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 · Dremio ⇄ 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.
Dremio SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dremio and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dremio and Splunk: authenticate both systems, choose the objects to sync (such as Dremio's Spaces and folders and Reflections), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Dremio: Arrow Flight SQL, JDBC/ODBC, and a REST API. Authentication: Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud. 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: Splunk exposes two API surfaces: the management REST API (default port 8089) for search jobs, saved searches, KV Store, indexes, users, and roles, and the HTTP Event Collector (default port 8088, port 443 on Splunk Cloud) for pushing events and metrics in — so the connector both reads from and writes into Splunk. Dremio: Dremio queries data in place on lake storage (S3, ADLS, HDFS) rather than ingesting it, so syncs read through Dremio to underlying files and Iceberg tables. Stacksync's field mapping accounts for these differences between Dremio 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 Dremio and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dremio and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dremio–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dremio 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 406 integrations available for Dremio and Splunk.
Popular · 7 of 406
-
Dremio ⇄ Pendo -
Dremio ⇄ Mixpanel -
Dremio ⇄ Microsoft Power Bi -
Splunk ⇄ Yellowbrick -
Splunk ⇄ Snowflake -
Splunk ⇄ BigQuery -
Splunk ⇄ MotherDuck
No integrations match .
