Weave Code
Laravel-native observability UI for cboxdk/laravel-telemetry: query Tempo, Loki and Prometheus/Mimir directly and visualize your apps with extensible Livewire cards.
Frequently asked questions about Laravel Telemetry Ui
- Can I use this package if my Laravel app doesn’t use Livewire?
- No, the package relies on Livewire components for its UI. If your app uses Blade-only or SPAs (Inertia/Vue/React), you’d need to rewrite the Livewire components or use Inertia to bridge them, which adds complexity. Consider alternatives like Grafana plugins if Livewire isn’t an option.
- What Laravel versions does this package support?
- The package targets modern Laravel versions (likely 9.x+ based on Livewire integration), but the README doesn’t specify exact versions. Check the `composer.json` or GitHub issues for compatibility notes. Always test in a staging environment first.
- Do I need to deploy Tempo, Loki, and Prometheus/Mimir before using this?
- Yes, this package assumes you already have Tempo (traces), Loki (logs), and Prometheus/Mimir (metrics) running and accessible. If you lack these, you’ll need to deploy and configure them first, which can be resource-intensive. Consider managed services like Grafana Cloud if self-hosting isn’t feasible.
- How do I secure access to the observability UI?
- The package doesn’t include built-in RBAC or authentication for the UI. You’ll need to implement Laravel’s built-in auth (e.g., middleware, gates) or integrate with your existing security layer. Avoid exposing the UI publicly without rate limiting and IP restrictions.
- Will this package slow down my Laravel app?
- Potential performance risks include Livewire component latency if Tempo/Loki queries are slow, and additional load on Prometheus/Mimir for scraping metrics. Optimize your observability stack (e.g., query caching, sampling) and monitor UI response times in staging.
- Can I customize the Livewire dashboards or add my own metrics?
- Yes, the package is designed to be extensible. You can create custom Livewire cards for your metrics or override existing components. Check the `resources/views` directory for templates and the Livewire docs for component inheritance patterns.
- What happens if my telemetry data isn’t in OpenTelemetry format?
- The package assumes `laravel-telemetry` is emitting OpenTelemetry-compatible data. If your traces/logs/metrics use a different format, you’ll need to pre-process them or modify the package’s query logic. Verify compatibility by inspecting the raw data before integration.
- Are there alternatives to this package for Laravel observability?
- Yes. For self-hosted stacks, Grafana with Prometheus/Loki plugins is a mature alternative. Commercial tools like Datadog or New Relic offer Laravel integrations with less setup. If you’re using OpenTelemetry, consider OTLP-compatible UIs like Jaeger or Tempo’s built-in UI.
- How do I test this package in a staging environment?
- Start by mocking Tempo/Loki/Prometheus responses (e.g., with Docker containers or local instances). Use Laravel’s `config:publish` to customize the package’s settings, then test Livewire components in isolation. Validate queries with tools like `curl` or Postman before full deployment.
- Is this package actively maintained? Should I use it in production?
- The package shows no recent activity (last release placeholder in 2026) and lacks stars/dependents, indicating unproven stability. Use it cautiously in production, especially for critical observability. Monitor GitHub issues for bugs and consider forking if maintenance is a concern.
Weaver
How can I help you explore Laravel packages today?