Weave Code
Loggastic Laravel Package
locastic/loggastic
Loggastic is a Laravel package for logging user activity and model changes. It records who did what and when, helping you build audit trails and simplify debugging. Lightweight and easy to drop into existing Laravel applications.
Symfony bundle for logging activity logs to ElasticSearch
Frequently asked questions about Loggastic
- Is Loggastic a Laravel package or a Symfony bundle?
- Despite being described as a Laravel package, Loggastic 2.1.0 is still structured as a Symfony bundle. It ships no Laravel service provider, facade, publishable config, or Laravel integration tests. In practice, you would need to port or wrap it before using it in a Laravel app.
- Which Laravel versions does Loggastic support?
- Loggastic 2.1.0 does not declare a Laravel version support matrix and does not ship Laravel integration tests, so there is no official out-of-the-box Laravel compatibility. It remains a Symfony bundle without a service provider or facade. You would need to write and test your own Laravel integration layer.
- How do I install Loggastic in a Laravel application?
- There is no documented Laravel install path with a service provider or publishable config in 2.1.0. You can require the Composer package, but you should expect to add your own service provider, configuration, and event listeners. For most Laravel teams, a purpose-built Laravel auditing package is a shorter path.
- Does Loggastic require Elasticsearch?
- Not anymore in 2.1.0. The package now supports storage: elasticsearch, doctrine, or in_memory, and when you choose a non-Elasticsearch backend it does not register Elasticsearch services, clients, or PSR-18 requirements. The Doctrine backend is the more portable option for relational databases.
- Can Loggastic store audit logs in MySQL, PostgreSQL, or SQLite?
- Yes, through its Doctrine DBAL backend. It targets DBAL 3.8+ and 4.x, works on PostgreSQL, MySQL, and SQLite, uses JSON columns with an indexed discriminator, normalizes timestamps to UTC, and performs tracker writes as upserts. That schema is a solid reference, though Laravel teams will likely want to recreate it with migrations.
- Does Loggastic use Laravel migrations for its log tables?
- No. The Doctrine adapter creates its schema through the DBAL schema API rather than Laravel migrations. That creates a schema ownership conflict if your team expects php artisan migrate to be the source of truth. Reconciling those mechanisms is a real integration hazard.
- How does Loggastic compare to spatie/laravel-activitylog?
- Loggastic is conceptually similar in that it records model activity, but it is not a native Laravel package in 2.1.0. Spatie's package is Laravel-first, migration-driven, and widely adopted, while Loggastic is a single-vendor Symfony bundle with 38 stars and no dependents. Choose Loggastic only if you plan to extract its storage and schema ideas.
- Is Loggastic actively maintained and production ready?
- Maintenance evidence is weak: 38 GitHub stars, zero dependents, and single-vendor ownership mean abandonment is a realistic risk. The 2.1.0 release adds a substantive storage abstraction, which is mildly positive, but it does not add Laravel integration. Treat it as a reference implementation rather than a drop-in production dependency for Laravel.
- What are the biggest risks of adopting Loggastic in a Laravel app?
- The main risks are poor Laravel stack fit, a hard doctrine/dbal dependency that reintroduces a second DB abstraction beside Eloquent, and schema ownership conflict with Laravel migrations. Vendor abandonment and Symfony major-version coupling remain concerns. Licensing is clean under MIT, so extracting and owning the useful parts is viable.
- How can I test Loggastic without running an Elasticsearch cluster?
- Use the in_memory storage backend added in 2.1.0. It gives you a working reference for sort, pagination, and per-class isolation semantics without provisioning a cluster. That makes a spike or port evaluation feasible in hours to a day rather than requiring Elasticsearch infrastructure.
Weaver
How can I help you explore Laravel packages today?