Weave Code
Nova Telescope Laravel Package
genealabs/nova-telescope
Brings Laravel Telescope into Laravel Nova, letting you browse requests, exceptions, queries, logs, and other Telescope entries directly from your Nova dashboard. Adds a convenient monitoring tool so you can inspect and debug application activity without leaving the admin panel.
A Laravel Nova tool.
Frequently asked questions about Nova Telescope
- What does genealabs/nova-telescope do?
- It renders Laravel Telescope entries inside Laravel Nova, so you can browse requests, exceptions, queries, logs, and other Telescope data from the Nova admin panel instead of switching to the Telescope UI. It is a presentation-layer Nova tool, meaning Telescope must already be installed and capturing data. It adds no telemetry, storage, or alerting of its own.
- How do I install genealabs/nova-telescope?
- Install it with Composer and register the tool in NovaServiceProvider::tools(). It assumes Laravel 10 or 11, a licensed Nova installation, and an existing Telescope installation. The supplied README excerpt is minimal, so verify the exact tool class and registration syntax before deploying.
- Which Laravel and Nova versions does it support?
- Release 11.0 claims Laravel 10 and 11, but the supplied information does not state the supported Nova major, Telescope version range, or PHP floor. Because the repository is archived, treat compatibility as frozen at that release. Test against your exact Nova and Telescope versions before adopting.
- Do I need Laravel Telescope installed already?
- Yes. The package does not collect or store telemetry; it only displays data that Telescope has already recorded. You need a working Telescope installation with its migrations and storage configured. Without Telescope capturing entries, the Nova tool has nothing to show.
- Does it inherit Telescope's authorization rules or only Nova's?
- This is unclear from the supplied evidence and should be verified before use. Nova's tool-level authorization and Telescope's own gate are separate controls, and if the tool reads Telescope storage directly under Nova auth, more people may see Telescope payloads than intended. Test both paths and confirm the effective audience.
- Is genealabs/nova-telescope still maintained?
- No, the repository is archived, with no upstream for compatibility fixes, security patches, or Nova-major updates. Adoption is easy, but long-term ownership is not free because every fix becomes internal work. Treat it as code you are forking and supporting yourself.
- Is it safe to use in production?
- It is operationally simple but exposes highly sensitive data such as request payloads, headers, cookies, session identifiers, SQL bindings, and stack traces. Route it through security review, restrict access, and confirm authorization equivalence. The archived status also means an unpatched renderer in the admin plane is a standing security finding.
- What alternatives exist to nova-telescope?
- A Nova nav link to /telescope can cover the same need in hours, and a thin custom Nova tool wrapping Telescope behind Nova's gate typically takes one to three engineer-days. Both avoid taking on an archived dependency. If Nova is not already your admin system of record, skip the integration entirely.
- Does it read Telescope's database tables directly or proxy Telescope routes?
- The supplied evidence does not say, and the answer changes your upgrade risk. Direct table reads are schema-coupled, while route proxying is version-coupled to Telescope. Inspect the source or test against your Telescope version to determine which model applies.
- How do I test it before rolling out?
- Install it in a non-production environment with the same Nova and Telescope versions you run in production. Generate representative Telescope entries, check that users with and without Telescope access see the right data, and verify it survives your Nova asset build. Confirm the tool still works after Nova or Telescope upgrades before relying on it.
Weaver
How can I help you explore Laravel packages today?