Real-time
Two-way sync
Changes in InterSystems IRIS or Splunk instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Analytics
InterSystems IRIS to Splunk integration — real-time, two-way sync
Keep InterSystems IRIS 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 InterSystems IRIS and Splunk
Give Splunk the users, events, and records that live in InterSystems IRIS in real time, and sync the cohorts and scores Splunk computes back into InterSystems IRIS where your applications read them.
A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Splunk is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from InterSystems IRIS into Splunk usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.
Stacksync syncs Namespaces, Stored Procedures, Tables, Views in InterSystems IRIS with HTTP Event Collector, Users and Roles, Dashboards, Search Results in Splunk in real time and in both directions. Operational rows flow into Splunk as they change, so dashboards read current data with no pipeline to maintain, and the segments, cohorts, or scores Splunk computes flow back into InterSystems IRIS, where the applications and services that read from it get them at normal query latency. Field-level mapping, schema and type translation, and conflict resolution are handled for you.
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 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
- 04 Replicate IRIS tables to Postgres so application teams can build against a familiar database
Common sync patterns
Analytics on live operational data, minus the pipeline
The users, events, orders, and records stored in InterSystems IRIS land in Splunk as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.
One version of each user or account
A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.
Filter and grouping dimensions kept fresh
Attributes teams slice by, such as plan, region, or account owner, stay current in Splunk because they sync from InterSystems IRIS as they change, instead of going stale after a one-time import.
What you can sync between InterSystems IRIS 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.
| InterSystems IRIS objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Views SQL views expose curated slices of data for outbound replication. | 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. | Views is specific to InterSystems IRIS and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Schemas Schema organization scopes which tables a sync connection can see. | 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 InterSystems IRIS and Dashboards to Splunk — each maps to any object or custom field on the other side. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through 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. | Persistent Classes is specific to InterSystems IRIS and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | 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. | Globals is specific to InterSystems IRIS and Saved Searches to Splunk — each maps to any object or custom field on the other side. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | 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. | Namespaces is specific to InterSystems IRIS and Fired Alerts to Splunk — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | 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. | Stored Procedures is specific to InterSystems IRIS and KV Store Collections to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between InterSystems IRIS 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.
InterSystems IRIS Splunk Interval-based propagation
DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk InterSystems IRIS 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 InterSystems IRIS as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- InterSystems IRIS: Constrained by database resources rather than published 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 InterSystems IRIS ⇄ Splunk
Connect InterSystems IRIS and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever InterSystems IRIS 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 InterSystems IRIS or Splunk record.
Observability
Monitoring
Track your InterSystems IRIS ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Splunk.
How the InterSystems IRIS and Splunk connectors work
InterSystems IRIS
- Integration surface
- SQL over JDBC/ODBC, plus object and REST access layers
- Authentication
- Database credentials
- Change detection
- Polling (timestamp or query-based); no standard webhook surface
- Capabilities
- read · write
- Rate limits
- Constrained by database resources rather than published 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 InterSystems IRIS 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 InterSystems IRIS 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.
InterSystems IRIS
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the InterSystems IRIS 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 · InterSystems IRIS ⇄ 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.
InterSystems IRIS SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
InterSystems IRIS and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between InterSystems IRIS and Splunk: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Views and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Splunk side: HTTP Event Collector, Users and Roles, Dashboards, Search Results, plus custom fields where Splunk exposes them. On the InterSystems IRIS side: Namespaces, Stored Procedures, Tables, Views. 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.
-
Common patterns for InterSystems IRIS and Splunk: Analytics on live operational data, minus the pipeline; One version of each user or account; Filter and grouping dimensions kept fresh. The users, events, orders, and records stored in InterSystems IRIS land in Splunk as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.
-
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. 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: Indexed events are immutable and time-stamped, so incremental extraction advances an earliest/latest window over _time (or _indextime) rather than using a modified-date CDC feed. InterSystems IRIS: Standard JDBC and ODBC drivers are available, which lets IRIS participate in database-style sync pipelines without a vendor-specific client. Stacksync's field mapping accounts for these differences between InterSystems IRIS and Splunk without custom code.
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 439 integrations available for InterSystems IRIS and Splunk.
Popular · 7 of 439
-
InterSystems IRIS ⇄ Pendo -
InterSystems IRIS ⇄ Mixpanel -
InterSystems IRIS ⇄ Microsoft Power Bi -
Splunk ⇄ Amazon Lightsail -
Splunk ⇄ Apache Cassandra -
Splunk ⇄ Azure Cosmos DB -
Splunk ⇄ Azure SQL Database
No integrations match .
