Skip to content
Database ⇄ Analytics

SAP Hana to Splunk integration — real-time, two-way sync

Keep SAP Hana 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 SAP Hana and Splunk

Give Splunk the users, events, and records that live in SAP Hana in real time, and sync the cohorts and scores Splunk computes back into SAP Hana 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 SAP Hana 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 Sequences, Triggers, System-versioned temporal tables, System views (SYS schema) in SAP Hana with Search Results, Saved Searches, Fired Alerts, KV Store Collections 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 SAP Hana, 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 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 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
  • 04 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.

Common sync patterns

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 SAP Hana as they change, instead of going stale after a one-time import.

Where Splunk tracks product events: behavior onto stored records

Signup, usage, and lifecycle events captured in Splunk sync into SAP Hana as rows, so applications and internal tools can read behavioral data next to the records they already keep.

Where Splunk builds cohorts or scores: results your services can read

Segments, cohorts, or scores computed in Splunk sync back into SAP Hana, where the services that read from the database act on them at query speed without calling the analytics API.

What you can sync between SAP Hana 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.

SAP Hana objects Splunk objects How this pairing syncs
Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. 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. Sequences is specific to SAP Hana and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side.
Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. 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. Triggers is specific to SAP Hana and Users and Roles to Splunk — each maps to any object or custom field on the other side.
System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. 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. System-versioned temporal tables is specific to SAP Hana and Dashboards to Splunk — each maps to any object or custom field on the other side.
System views (SYS schema) Catalog and monitoring views such as SYS.TABLES and TABLE_COLUMNS; read to discover schema and auto-generate field mappings for new tables. 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. System views (SYS schema) is specific to SAP Hana and Search Results to Splunk — each maps to any object or custom field on the other side.
Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. 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. Column store tables is specific to SAP Hana and Saved Searches to Splunk — each maps to any object or custom field on the other side.
Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. 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. Row store tables is specific to SAP Hana and Fired Alerts to Splunk — each maps to any object or custom field on the other side.

How changes propagate between SAP Hana 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.

SAP Hana Splunk Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
  • 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 SAP Hana ⇄ Splunk

Connect SAP Hana and Splunk for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SAP Hana–Splunk connection.

Real-time

Two-way sync

Changes in SAP Hana or Splunk instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever SAP Hana 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 SAP Hana or Splunk record.

Observability

Monitoring

Track your SAP Hana ⇄ Splunk sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between SAP Hana and Splunk.

How the SAP Hana and Splunk connectors work

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.

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 SAP Hana 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.

  1. 01

    Connect your apps

    Authenticate SAP Hana 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    SAP Hana connected
    Splunk connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the SAP Hana 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · SAP Hana ⇄ Splunk
    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
    SAP Hana Splunk
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

SAP Hana and Splunk 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 512 integrations available for SAP Hana and Splunk.

Popular · 8 of 512
All SAP Hana integrations All Splunk 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