- How do I install andrey-helldar/sentriable-laravel in a Laravel app?
- Run composer require andrey-helldar/sentriable-laravel. Laravel auto-discovery registers the service provider, and you can publish the package config with the usual vendor:publish command. If you plan to use the model linkage, also publish and run the package migration and add the trait to the relevant Eloquent models.
- Does sentriable-laravel replace sentry/sentry-laravel?
- No. It is a lightweight wrapper and leaf dependency that sits alongside sentry/sentry-laravel, and it does not replace the SDK, intercept the error pipeline, or own Sentry configuration. You still need Sentry installed and configured in the application. It simplifies native Laravel usage through a dedicated log channel, helpers, facade, and optional model linkage.
- Which PHP and Laravel versions does sentriable-laravel support?
- Confirm support from the package composer.json rather than from release notes alone. The v2.1.0 notes reportedly lack a change description, so read the compare diff and check the php and illuminate constraints before bumping. If the diff narrows constraints, treat that as a breaking change for services on older Laravel minors.
- How do I send an exception or custom message to Sentry with Sentriable?
- Use the included helpers or facade, or route messages through the dedicated sentry log channel with Log::channel('sentry'). This keeps reporting native to Laravel and avoids touching the low-level Sentry client directly. It is intended for capturing exceptions and custom messages without extra SDK glue.
- How do I configure the Sentry log channel in Laravel?
- Publish the package config and configure the sentry channel alongside your existing Sentry SDK settings and DSN. Then call Log::channel('sentry') or use the package helpers and facade from application code. Keep the DSN and environment-specific values in your normal Laravel environment configuration.
- Does sentriable-laravel work with Laravel's exception handler and queue workers?
- It is designed to play nicely with Laravel's exception handler and queue workers. You may still need application glue in the exception handler or queued job failed hooks to record Sentry event identifiers against domain models. The package supplies integration points, not the per-application workflow logic.
- What is the sentriable polymorphic relation used for?
- It lets Eloquent models be tied to Sentry issue or event records, which is useful when triaging alerts against entities such as orders, tenants, or jobs. Using it requires publishing and running the package migration and adding the trait to the relevant models. Adopt it only if your team has a real triage workflow that consumes that linkage; otherwise it adds a table and trait with no consumer.
- How do I upgrade sentriable-laravel from v2.0.1 to v2.1.0?
- The expected semver-minor path is a constraint bump plus composer update with no application code changes. That expectation is unverified because the v2.1.0 release notes provide only an auto-generated compare link. Read the diff and check composer.json for changed php or illuminate requirements before the bump lands on a shared branch, and treat constraint narrowing as breaking.
- Is sentriable-laravel safe and maintained for production use?
- The dominant risk is single-author maintenance and bus factor rather than necessarily code quality. The v2.1.0 release lacks a changelog body, so verify the diff and pin or constrain the version appropriately. Also decide a retention policy for stored Sentry references and have a fork-or-vendor contingency if upstream maintenance goes quiet.
- When should I avoid sentriable-laravel or use an alternative?
- Defer adoption if you do not already run Sentry in production with alerting and a real triage process, or if no models genuinely need issue linkage. Using sentry/sentry-laravel directly or an existing in-house equivalent may be a better fit. Before adding a second integration, check for class or trait name collisions and duplicate migration publishing.