Skip to content
Data warehouse ⇄ Developer tools

Apache Druid to PagerDuty integration — real-time, two-way sync

Keep Apache Druid and PagerDuty 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 Apache Druid and PagerDuty

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

Apache Druid is the central store where teams keep Segments, Dimensions, Metrics, Ingestion Supervisors for reporting and analysis; PagerDuty 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 Services, Users, Teams, Schedules produced in PagerDuty are exactly what analysts want to measure in Apache Druid, and the curated rows in Apache Druid are what should drive the next action in PagerDuty. 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 Segments, Dimensions, Metrics, Ingestion Supervisors in Apache Druid with Services, Users, Teams, Schedules in PagerDuty 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 Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.
  • 02 Sync Druid query results into a warehouse to combine real-time aggregates with historical models.
  • 03 Provision and deactivate Users and Team memberships two-way from an HRIS or identity provider so the on-call roster matches the current org.
  • 04 Write Schedules and Escalation Policies from a workforce tool or source-of-truth spreadsheet so rotations and overrides stay consistent across teams.

Common sync patterns

Operational data lands in Apache Druid for analytics

Records created in PagerDuty — issues, events, messages, metrics, or user changes — replicate into Apache Druid tables as they happen, so reporting runs on current data instead of last night's export.

Warehouse signals reach PagerDuty

A row scored, flagged, or enriched in Apache Druid creates or updates the matching record in PagerDuty, so the operational tool acts on the same data the analysts already see.

Backfill history, then stay live

Load the existing set of Services, Users, Teams, Schedules into Apache Druid once, then keep it current with every change — you get full history plus real-time updates without a separate pipeline.

What you can sync between Apache Druid and PagerDuty

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.

Apache Druid objects PagerDuty objects How this pairing syncs
Dimensions String and categorical columns used for filtering and grouping in synced queries. Incidents Core records with status of triggered, acknowledged, or resolved plus urgency and assignments; created, updated, and resolved two-way, with V3 webhooks firing on each transition. Dimensions is specific to Apache Druid and Incidents to PagerDuty — each maps to any object or custom field on the other side.
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Services Technical services that group incidents and hold integration keys; read and written two-way, with service.created, service.updated, and service.deleted webhook events. Metrics is specific to Apache Druid and Services to PagerDuty — each maps to any object or custom field on the other side.
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Users Responders with contact methods and notification rules; provisioned and updated two-way to keep the on-call roster aligned with an HRIS or identity provider. Ingestion Supervisors is specific to Apache Druid and Users to PagerDuty — each maps to any object or custom field on the other side.
Lookups Key-value mappings joined at query time, refreshable from external systems. Teams Groupings of users, services, and escalation policies; synced two-way so membership mirrors org structure from an IdP or HRIS. Lookups is specific to Apache Druid and Teams to PagerDuty — each maps to any object or custom field on the other side.
Tasks Batch ingestion and compaction jobs monitored during data loads. Schedules On-call rotations built from layers and overrides; read and written so calendar or workforce tools can drive who is on call. Tasks is specific to Apache Druid and Schedules to PagerDuty — each maps to any object or custom field on the other side.
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Escalation Policies Ordered rules routing incidents to users and schedules; read and written two-way to codify paging logic from a source of truth. Datasources is specific to Apache Druid and Escalation Policies to PagerDuty — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid and PagerDuty

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.

Apache Druid PagerDuty Interval-based propagation

DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.

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

PagerDuty Apache Druid Sub-second propagation

DetectionPagerDuty notifies Stacksync of record changes through webhook events. V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated).

DeliveryEach detected change is applied to Apache Druid as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
  • PagerDuty: REST API allows 960 requests per minute per token and returns HTTP 429 when exceeded; the Events API is rate-limited separately per integration key.
What ships with Apache Druid ⇄ PagerDuty

Connect Apache Druid and PagerDuty for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–PagerDuty connection.

Real-time

Two-way sync

Changes in Apache Druid or PagerDuty instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Druid or PagerDuty 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 Apache Druid or PagerDuty record.

Observability

Monitoring

Track your Apache Druid ⇄ PagerDuty sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Druid and PagerDuty.

How the Apache Druid and PagerDuty connectors work

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

PagerDuty

Integration surface
REST API v2 (plus Events API v2 for inbound alerts)
Authentication
REST API token via the Authorization: Token header (account-level for full access or user-level scoped to the user's permissions), or OAuth 2.0 (Authorization Code / PKCE); the Events API v2 uses a per-service routing (integration) key
Change detection
V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated); list endpoints also support polling with updated_at and since/until windows
Capabilities
read · write · webhooks
Rate limits
REST API allows 960 requests per minute per token and returns HTTP 429 when exceeded; the Events API is rate-limited separately per integration key.
PagerDuty setup guide
How it works

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

    Choose tables

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

Apache Druid and PagerDuty 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 319 integrations available for Apache Druid and PagerDuty.

Popular · 7 of 319
All Apache Druid integrations All PagerDuty 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