Weave Code
Log Laravel Package
orchid/log
Logging for Laravel Orchid: capture application events and review them right in your admin panel. orchid/log gives teams a simple way to monitor activity, trace issues, and maintain an audit trail without leaving the Orchid dashboard.
Orchid CMS logging package
Frequently asked questions about Log
- What is orchid/log used for?
- orchid/log is the logging feature of the Orchid Platform, published as a subtree split of theOrchid/Platform repository rather than a standalone Laravel logging library. It captures application events such as Eloquent model changes and surfaces them inside the Orchid admin panel so business users can review activity and maintain an audit trail. It is not a replacement for engineering-facing diagnostics like Sentry, Datadog, or Telescope.
- Do I need to install orchid/log separately?
- In practice no: it arrives as a transitive dependency of orchid/platform, so installing the platform pulls it in automatically. Adding just this package to an application that does not run Orchid produces an unsupported hybrid with high cost and low value. Install orchid/platform and let Composer resolve the matching log version.
- Which Laravel and PHP versions does orchid/log support?
- Its illuminate/* and PHP constraints track the corresponding Orchid Platform release, so the supported matrix is whatever that platform tag declares. There is no independent support window, so pin exact versions against the platform release instead of floating the constraint. Check the composer.json and CI matrix of the matching orchid/platform tag before committing.
- How do I enable logging on a model?
- Apply the package's logging trait to the Eloquent models you want to track, and Orchid records create, update, and delete events with attribute-level snapshots. Configuration such as the redaction list is set on the trait per model, not globally in code review. Make sure the package migrations for the log table have run in your environment.
- Does orchid/log require the Orchid admin panel to work?
- Yes. The package renders inside the Orchid dashboard and depends on platform internals that are not a published contract, so there is no supported headless mode. It writes to your application database, but reviewing the entries expects the Orchid UI. If you are not running Orchid, use a general-purpose activity log library instead.
- Will orchid/log slow down my application?
- Logging is dispatched synchronously inside Eloquent model event handlers, which adds write amplification to every mutating request. Confirm whether your pinned version supports queueing the log write and enable it if so. Also be aware that a logging failure can be dragged into a legitimate business transaction when the write happens inline.
- How do I keep passwords and tokens out of the logs?
- Maintain an explicit redaction list in the trait configuration rather than relying on code review to catch leaks. Attribute-level snapshots can otherwise capture PII, secrets, and token material from your models. Revisit the redaction list whenever you add a new model to the logging set.
- How do I prune or retain old log entries?
- Retention mechanics depend on the platform version, so check whether pruning is built in or whether you need a scheduled command to delete old rows. Plan the schema and indexes so the log table does not degrade query performance as it grows. If you need long-term or tamper-proof retention, scope an external system of record separately.
- How does orchid/log compare to Telescope, Sentry, or spatie/laravel-activitylog?
- They serve different audiences. Telescope, Sentry, and Datadog are engineering diagnostics for tracing issues, while orchid/log is a business-facing activity trail rendered in the admin panel. spatie/laravel-activitylog is a general-purpose activity logger you can adopt without Orchid. Many teams run both: diagnostics on Sentry or Telescope and audit visibility in Orchid.
- Is orchid/log actively maintained?
- It is a subtree split of the Orchid Platform monorepo, so its release cadence follows the platform and the split repo routinely lags the main repository. Judge project health by the platform repo rather than the split's stars or dependent count, which are distribution artifacts. It is a single-maintainer ecosystem with no vendor SLA, so pin exact tags and verify tag parity before upgrading.
Weaver
How can I help you explore Laravel packages today?