Telemetry UI for Laravel
Observability UI for Laravel that replaces Grafana for app-level monitoring. Queries your existing Tempo, Loki and Prometheus backends directly, with Laravel-shaped screens from metric aggregate down to the single trace.
Telemetry UI for Laravel is the presentation counterpart to Telemetry for Laravel. It queries your existing Tempo, Loki and Prometheus or Mimir backends directly, with no agent and no vendor cloud, and renders the answers as screens shaped like Laravel instead of general-purpose panels. It is schema-aware of every metric and span attribute the core package emits, so the screens are built for the data rather than assembled from it.
Observability Shaped Like Laravel
Laravel-Shaped Screens
Dashboard, requests, jobs, commands, scheduled tasks, exceptions, queries, cache, outgoing HTTP, mail and notifications, users, logs and system. Not panels you assemble, screens that already know the framework.
Aggregate to Trace
Every screen cross-links from the metric aggregate to the individual trace. Spot a slow route in the histogram, land in its waterfall two clicks later.
Fleet-Aware
A service and environment switcher scopes every screen. One installation covers every app reporting to the same backends.
Autodetecting Families
Optional schema families light up their own pages when their metrics exist. Install Statamic Telemetry and the Statamic screens appear on their own.
Livewire Card Extensibility
Packages and apps add pages with PHP and Blade plus any PromQL, TraceQL or LogQL query. No JavaScript build required.
Inert When Idle
Boot registers class-string maps only, and one env var disables everything. Access is gated by a viewTelemetryUi gate, local-only by default.
When Grafana is too generic
Grafana is the right home for fleet-level monitoring, and the telemetry family ships dashboards for it. But a wall of general-purpose panels answers general-purpose questions. When the question is "what did this queue job actually do" or "which route is burning the CPU budget", the answer deserves a view built for Laravel: queue timelines, trace waterfalls and request breakdowns rendered inside a UI that speaks the vocabulary of the framework, at /telemetry-ui in the app you already run.
Early days
The package is in alpha. It expects the Grafana stack backends (Tempo, Loki, Prometheus or Mimir) that Telemetry for Laravel exports to, and it reads them directly over their HTTP APIs.
