Skip to content
Data warehouse ⇄ Developer tools

ClickHouse to PagerDuty integration — real-time, two-way sync

Keep ClickHouse 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 ClickHouse and PagerDuty

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

ClickHouse is the central store where teams keep Dictionaries, Tables (MergeTree family), Databases, Views 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 On-Calls, Notes and Log Entries, Incidents, Services produced in PagerDuty are exactly what analysts want to measure in ClickHouse, and the curated rows in ClickHouse 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 Dictionaries, Tables (MergeTree family), Databases, Views in ClickHouse with On-Calls, Notes and Log Entries, Incidents, Services 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 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
  • 02 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
  • 03 Write Schedules and Escalation Policies from a workforce tool or source-of-truth spreadsheet so rotations and overrides stay consistent across teams.
  • 04 Mirror Services and their integration keys with a CMDB or service catalog so ownership and tier metadata stay aligned in both directions.

Common sync patterns

Warehouse signals reach PagerDuty

A row scored, flagged, or enriched in ClickHouse 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 On-Calls, Notes and Log Entries, Incidents, Services into ClickHouse once, then keep it current with every change — you get full history plus real-time updates without a separate pipeline.

No batch jobs to babysit

New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.

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

ClickHouse objects PagerDuty objects How this pairing syncs
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. On-Calls Computed view of who is on call now, derived from schedules and escalation policies; read-only, ideal for pushing current responders into other systems. Materialized views is specific to ClickHouse and On-Calls to PagerDuty — each maps to any object or custom field on the other side.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. Notes and Log Entries Notes are writable to append context to an incident; log entries are a read-only record of every action taken on that incident. Distributed tables is specific to ClickHouse and Notes and Log Entries to PagerDuty — each maps to any object or custom field on the other side.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. 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. Dictionaries is specific to ClickHouse and Incidents to PagerDuty — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. 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. Tables (MergeTree family) is specific to ClickHouse and Services to PagerDuty — each maps to any object or custom field on the other side.
Databases Namespaces that group tables and scope permissions for sync users. 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. Databases is specific to ClickHouse and Users to PagerDuty — each maps to any object or custom field on the other side.
Views Saved queries used as curated, read-only sync sources. Teams Groupings of users, services, and escalation policies; synced two-way so membership mirrors org structure from an IdP or HRIS. Views is specific to ClickHouse and Teams to PagerDuty — each maps to any object or custom field on the other side.

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

ClickHouse PagerDuty Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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

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

Rate-limit considerations

  • 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 ClickHouse ⇄ PagerDuty

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the ClickHouse and PagerDuty connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

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 ClickHouse 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 ClickHouse 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
    ClickHouse connected
    PagerDuty connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

ClickHouse 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 419 integrations available for ClickHouse and PagerDuty.

Popular · 8 of 419
All ClickHouse 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