PulsusDB
by digitalis.io GitHub
Open protocols in both directions

Connect your stack
Keep your workflows

Ship telemetry from AWS, Azure, GCP, Kubernetes, applications and infrastructure through OpenTelemetry, then query PulsusDB from Grafana® software, Perses and the tools your teams already know

Explore integrations Read API compatibility
integration.mapSHIP ONCE · QUERY ANYWHERE
PRODUCE
AppsServicesInfrastructure
COLLECT
OTel Collectorbatch · retry · route
STORE + QUERY
PulsusDBOpen APIs · ClickHouse® database
EXPLORE
Grafana® softwarePersesHTTP API
LOGSMETRICSTRACESPROFILES
OTLPPROMETHEUS APILoki® APITempo® APIPyroscope™ APIREMOTE WRITE
The primary ingestion path

OTel Collector
Into PulsusDB

The OpenTelemetry Collector, or another compatible distribution, receives telemetry from applications and infrastructure, then exports every signal to PulsusDB over standard OTLP. Put batching, retries, enrichment and routing in one vendor-neutral pipeline

OpenTelemetry Collector docs ↗
otel-config.yamlOTLP → PULSUSDB
01exporters:
02  otlphttp:
03    endpoint: https://pulsusdb:3100
04service:
05  pipelines:
06    logs:    { exporters: [otlphttp] }
07    metrics: { exporters: [otlphttp] }
08    traces:  { exporters: [otlphttp] }
standard OTLP/HTTPprotobuf or JSON
LogsPOST /v1/logs
MetricsPOST /v1/metrics
TracesPOST /v1/traces
ProfilesPOST /v1development/profiles
Cloud and cluster integrations

Bring the platform telemetry
Through OpenTelemetry

Cloud-native services expose metrics, logs and traces through different export systems. Collect or bridge those feeds into OTLP, preserve their resource identity and send one standard telemetry model into PulsusDB

01 / CLOUD

AWS

Accounts, regions and service dimensions stay attached to every signal

METRICSCloudWatch→OTel Collector
LOGSCloudWatch Logs · S3 · Kinesis→OTel gateway
TRACESADOT · OpenTelemetry SDKs→OTLP
EC2ECS / EKSLambdaRDSDynamoDBVPC
Explore AWS collection →
02 / CLOUD

Azure

Subscription, resource group, region and resource identity remain queryable

METRICSAzure Monitor→OTel Collector
LOGSDiagnostic Settings · Event Hubs→OTel gateway
TRACESOpenTelemetry SDKs→OTLP
Virtual MachinesAKSApp ServiceFunctionsAzure SQLNSG
Explore Azure collection →
03 / CLOUD

GCP

Project, zone, region and resource labels survive the collection boundary

LOGSCloud Logging · Pub/Sub→OTel gateway
METRICSCloud Monitoring→OTel Collector
TRACESOpenTelemetry SDKs→OTLP
Compute EngineGKECloud RunCloud FunctionsCloud SQLVPC
Explore GCP collection →
04 / CLUSTER

Kubernetes

Cluster, namespace, workload, pod, container and node identity travel together

METRICSPrometheus · kubelet · kube-state→OTel Collector
LOGSContainer output · cluster events→OTel Collector
TRACESOTel Operator · application SDKs→OTLP
NodesControl planeWorkloadsContainersEventsIngress
Explore Kubernetes collection →
MORE TELEMETRY SOURCES Applications → Databases → Network → AI and LLM →
Bring your own frontend

Keep the frontend
Keep the query language

PulsusDB implements the APIs the observability ecosystem already understands. Existing query editors, dashboards and team habits stay useful while the ClickHouse database becomes the storage and execution engine underneath

FULL OBSERVABILITY WORKSPACE01

Grafana® software

Use the built-in Grafana® data sources to explore all four signals in one interface

METRICSPrometheus data sourcePromQL
LOGSLoki® data sourceLogQL
TRACESTempo® data sourceTraceQL
PROFILESPyroscope™ data sourceProfile APIs
Metrics use the always-on Prometheus API. Enable PULSUS_COMPAT_ENDPOINTS for the Loki® API, Tempo® API and Pyroscope™ API compatibility endpoints
Read the data source documentation ↗
OPEN DASHBOARDS02

Perses

Point a Prometheus datasource at PulsusDB and keep building PromQL dashboards as code

PERSESPrometheusDatasource
PULSUSDB/api/v1
PromQL panelsVariablesAnnotationsProxy or direct
The Prometheus HTTP API is native and always on, so Perses needs no compatibility flag
Perses Prometheus plugin ↗
A deliberate compatibility model

Open standards first
Compatibility when needed

The primary PulsusDB APIs stay product-neutral. A single configuration flag adds third-party query aliases and foreign ingest receivers for migrations and existing tooling

InterfaceUse it forAvailability

OTLP/HTTP

Logs, metrics, traces and profiles from OpenTelemetry Collector or compatible distributions

Always on

Prometheus HTTP API

PromQL from Grafana® software, Perses and any Prometheus-compatible client

Always on

Prometheus remote write

Metrics from the Collector, Prometheus and compatible agents

Always on

Loki® API · Tempo® API · Pyroscope™ API

Existing data sources for Grafana® software, Explore workflows and compatible dashboards

Compatibility flag

Loki® API · Zipkin · Influx · Datadog · Elastic

Foreign-format ingestion while a pipeline moves toward OpenTelemetry

Compatibility flag
ONE SWITCHPULSUS_COMPAT_ENDPOINTS=true

Mount the optional aliases without changing the native PulsusDB APIs or the storage model underneath

Configuration guide ↗ Compatibility matrix