Telemetry Store for Laravel
A native ClickHouse OTEL store for Telemetry for Laravel. A PHP OTLP ingest endpoint plus a ClickHouse read driver for the Telemetry UI, so one SQL store replaces the Tempo, Loki and Mimir stack.
Telemetry Store for Laravel is a native ClickHouse OTEL store for Telemetry for Laravel. One SQL store instead of the Tempo, Loki and Mimir stack. It does two things: a native PHP OTLP/HTTP endpoint that receives the emitter traces, logs and metrics and writes them straight to ClickHouse with no OpenTelemetry Collector in the loop, and a ClickHouse-backed read driver for the Telemetry UI.
One Store, Every Signal
Collector-Free Ingest
A native PHP OTLP/HTTP endpoint receives traces, logs and metrics from the emitter and writes them straight to ClickHouse. Point TELEMETRY_OTLP_ENDPOINT at this app, no Collector sidecar.
ClickHouse Read Driver
Registers as an extra connection driver for the Telemetry UI. Every existing dashboard card runs against ClickHouse unchanged, because the UI query layer is a backend-neutral IR each driver compiles to its own dialect.
Selectable Per Connection
An additional backend, not a replacement. Point logs at ClickHouse while keeping metrics on Prometheus, or move everything over. Your call, per connection.
Collector-Compatible Schema
Modelled on the OpenTelemetry Collector clickhouseexporter tables: otel_logs, otel_traces and otel_metrics. MergeTree, partitioned by day, with per-signal TTL for cheap partition-drop retention.
Early
The schema, ClickHouse client and OTLP ingest are the first milestone. The read drivers land signal by signal, logs then traces then metrics, matching the difficulty of expressing each in SQL. rate() and histogram_quantile() over cumulative series is the hard part.
Install
composer require cboxdk/laravel-telemetry-store, then php artisan telemetry-store:install creates the ClickHouse tables idempotently. Configure the ClickHouse connection and ingest in config/telemetry-store.php or via env, then select the ClickHouse driver in telemetry-ui.connections. For production, ClickHouse host access, retention, securing the ingest endpoint and throughput, see the deployment docs.