Weave Code
Logmanager Laravel Package
backpack/logmanager
Backpack LogManager is a Laravel admin panel add-on for browsing, searching, and managing application log files directly from Backpack. It gives developers a convenient UI to preview logs, filter entries, and quickly diagnose issues without SSH.
An interface to preview, download and delete Laravel log files.
Frequently asked questions about Logmanager
- How do I install Backpack LogManager in a Laravel application?
- Install it with Composer as backpack/logmanager. The service provider is auto-discovered, so no manual registration is normally required. You then register the package's routes inside your Backpack admin panel and optionally publish its config file. There are no database migrations, so the install footprint is small.
- Which Laravel and Backpack versions does LogManager support?
- LogManager is a first-party module in the Laravel-Backpack ecosystem, so it targets apps already running Backpack 5 or 6 on Laravel 9 through 11. Check the composer.json constraints of the specific release before upgrading either Laravel or Backpack. If you are not on Backpack, the package is not a fit unless you plan to adopt the whole admin panel.
- Is it safe to expose log files in a production admin panel?
- Laravel logs routinely contain stack traces, environment values, request payloads, SQL fragments, session identifiers and occasionally credentials or PII. Previewing and downloading them in a browser creates a real data-handling obligation. Treat route access as a governed permission rather than a side effect of being an admin, and confirm whether log scrubbing or redaction is required before enabling it in production.
- Can I restrict who can view, download, or delete log files?
- Yes, but the enforcement is yours to configure. LogManager inherits authentication and middleware from Backpack, so it only knows what your Backpack guard and permission gates tell it. Map the package routes to an explicit permission instead of relying on generic admin role membership. Download and especially delete usually warrant a stricter gate than read-only preview.
- Does LogManager work with daily, stack, or stderr log channels?
- The package assumes locally readable log files in the expected log directory, which covers common single, daily and stack channels writing to disk. Apps logging only to stderr inside containers, or shipping to CloudWatch, Papertrail or Datadog, will see an incomplete or empty view. Validate it against your app's real channel configuration before relying on it during an incident.
- Will LogManager work on a multi-node or containerized deployment?
- Only if the log directory is on shared storage that every node can read. With per-container or per-node local logs, the panel shows just the file from whichever instance served the request. For horizontally scaled or ephemeral environments, a centralized log backend is a better fit than a file-based viewer.
- Is there an audit trail for who viewed or deleted a log file?
- LogManager does not provide an audit trail out of the box. The delete action is a plain UI affordance, so an admin can destroy forensic evidence during an incident unless you add your own controls. If compliance or post-incident review matters, log access and deletion through your own event or activity logging, and consider a retention policy outside the package.
- Does Backpack LogManager need any database tables or config changes?
- No migrations or schema changes are involved, which keeps the blast radius of installation low. Configuration is optional and mostly about publishing the package config and pinning it in version control. The main setup work is route registration and wiring the routes to the right permission gates.
- How does LogManager compare to Filament log viewers or Laravel Log Viewer?
- LogManager is not a general-purpose log viewer; it is an admin-panel surface built on Backpack's routing, menu and guard conventions. It fits naturally if your product is already standardized on Backpack, with near-zero architectural friction. If you are on Filament, Nova or a custom admin panel, a purpose-built read-only route or a Filament-specific viewer is the cheaper path.
- Is Backpack LogManager actively maintained, and what is its license?
- It is maintained under the Laravel-Backpack organization, which acts as the effective backstop even though the package has a narrow user base. Composer metadata reports a NOASSERTION license, so legal should confirm the actual terms before shipping it. Review the repository's release history and Backpack's upgrade cadence as part of your normal dependency review.
Weaver
How can I help you explore Laravel packages today?