Weave Code
Laravel Telemetry Ui Laravel Package
cboxdk/laravel-telemetry-ui
Grafana-replacement observability UI for Laravel. Query Tempo, Loki and Prometheus/Mimir directly; explore Laravel-shaped screens for routes, jobs, exceptions, hosts and users with drill-down and cross-signal correlation. No agent or vendor cloud.
Laravel Telemetry UI is a Grafana-style observability dashboard for Laravel that queries your existing Tempo, Loki and Prometheus/Mimir directly — no agent, no vendor cloud, data stays in your infrastructure. It's schema-aware of every metric and span attribute emitted by cboxdk/laravel-telemetry, making routes, jobs, queries and users first-class, cross-linked concepts.
- Laravel-shaped screens: Requests, Jobs, Commands, Schedule, Exceptions, Queries, Cache, Users, Hosts, Logs, trace waterfall.
- Purpose-built drill-down: click a route, job or host for a scoped detail page, not a generic search.
- Signal correlation: traces show host CPU/load/memory flagged against baselines.
- Annotations: deploy, incident and version markers on every chart.
Frequently asked questions about Laravel Telemetry Ui
- What is cboxdk/laravel-telemetry-ui used for?
- It is a Laravel-native observability UI for apps already using cboxdk/laravel-telemetry. It provides a versioned JSON API and a React SPA that query Tempo, Loki and Prometheus/Mimir directly, with Laravel-shaped screens for routes, jobs, commands, exceptions, queries, hosts and logs. It is a presentation layer, not a telemetry pipeline, store or collector.
- How do I install and configure cboxdk/laravel-telemetry-ui?
- Install it with Composer as cboxdk/laravel-telemetry-ui alongside its required cboxdk/laravel-telemetry dependency. Configure the three environment variables for your Tempo, Loki and Prometheus/Mimir datasource URLs, then define the viewTelemetryUi gate because it defaults to local-environment access only. You reach first render quickly if those backends already exist and are reachable from the app tier.
- Does laravel-telemetry-ui replace Grafana?
- It replaces Grafana only in the read-and-visualize sense: it queries your existing Tempo, Loki and Prometheus/Mimir endpoints and gives you Laravel-aware screens. It is not a telemetry pipeline, store or collector, and it does not ship an agent. The advantage is that the UI lives inside your Laravel app with your auth and Livewire stack, but you still need the observability backends behind it.
- Do I need Prometheus, Tempo and Loki already running to use this package?
- Yes, the package queries existing Tempo, Loki and Prometheus/Mimir endpoints directly, so it assumes an LGTM-compatible stack or willingness to stand one up. The README notes a backend-neutral query IR as of 1.0.0 with per-driver compilation, and a native ClickHouse store exists as a companion, so it is not permanently welded to LGTM. If you do not run those backends, factor the full cost of retention, operations and reachability from the app tier into the decision.
- How do I secure the Laravel telemetry UI in production?
- Access is gated by a viewTelemetryUi gate that defaults to the local environment only, so production exposure is an explicit decision someone must define. In multi-tenant apps you must use TelemetryUi::restrictScopeUsing() or the static scope lock to prevent cross-tenant data leakage, enforced at query time. Also do a data-classification pass because the UI can expose hosts, user identifiers, team, client IP, deployment metadata, exception payloads, query text and logs.
- Does laravel-telemetry-ui support multi-tenant Laravel applications?
- It can, but multi-tenant use requires explicit restriction through TelemetryUi::restrictScopeUsing() or the static scope lock. Enforcement happens at query time, so you should verify every screen and datasource query respects the tenant boundary. Treat the wide data exposure surface, including hosts, users, IPs, exceptions, query text and logs, as something to classify before broader rollout.
- What are the production performance risks of laravel-telemetry-ui?
- The main production risk is query cost shifted to your observability datasources. Every card, auto-refresh and Livewire update issues PromQL, TraceQL or LogQL against Tempo, Loki and Prometheus/Mimir, and the package does not describe a cache or aggregation layer. Monitor backend load and set refresh expectations before exposing it to many users.
- Is cboxdk/laravel-telemetry-ui stable enough for production?
- The README describes the package as alpha and warns that APIs may still shift, despite releases already past 1.0. The changelog shows breaking driver-contract changes at 1.0.0 and 0.3.0, and it is effectively a single-maintainer project with a fast-moving surface. Pin versions, read the changelog before upgrading, and plan a fork contingency.
- How does laravel-telemetry-ui depend on cboxdk/laravel-telemetry?
- cboxdk/laravel-telemetry is a hard dependency, and the UI is schema-aware of the metric and span attributes that package emits. Adopting the UI therefore means adopting the emitter's instrumentation conventions for span names, attribute keys, and route, job and query semantics. Emitter and UI versions must move together, so pin both because a Composer update in one can break the other.
- Which Laravel and PHP versions does laravel-telemetry-ui support?
- The README excerpt does not list minimum Laravel or PHP versions, so check the package's composer.json constraints and CHANGELOG before adopting it. It is a Laravel package that requires cboxdk/laravel-telemetry and uses the app's auth and Livewire stack. Pin versions and verify compatibility in a staging app before upgrading.
Weaver
How can I help you explore Laravel packages today?