Log Manager Laravel Package

Product Decisions This Supports

• Audit Logging & Compliance: Enables structured logging of custom events (e.g., user actions like logins/registrations) and system errors, critical for GDPR, SOX, or internal audits. Reduces manual log aggregation efforts.
• Observability Roadmap: Provides a lightweight, Laravel-native solution to centralize logs (vs. third-party tools like Sentry or Datadog) for early-stage products with tight budgets.
• Build vs. Buy: Avoids reinventing a custom logging system; leverages an MIT-licensed package with minimal maintenance overhead (vs. building from scratch).
• Use Cases:
  • Security: Track suspicious activity (e.g., failed logins) via custom log types.
  • Debugging: Centralize error logs with stack traces in a dedicated table (vs. scattered Laravel log files).
  • Analytics: Export log data to BI tools (e.g., via the logs table) for user behavior trends.

When to Consider This Package

• Adopt if:
  • Your Laravel app needs structured, queryable logs (e.g., filtering by log type, timestamp, or user).
  • You require minimal setup (no external services; uses Laravel’s built-in database).
  • Your team lacks resources to build a custom logging system but needs more than Laravel’s default logging.
  • You prioritize cost efficiency (MIT license, no SaaS dependencies).
• Look elsewhere if:
  • You need real-time log streaming (e.g., for DevOps teams) → Use Laravel Horizon + third-party tools (e.g., Logstash).
  • Your app uses non-Laravel PHP → This package is Laravel-specific.
  • You require advanced log analysis (e.g., correlation IDs, distributed tracing) → Consider Sentry, ELK Stack, or OpenTelemetry.
  • You have strict compliance needs (e.g., HIPAA) requiring immutable log storage → Evaluate dedicated audit log databases (e.g., AWS CloudTrail).
  • The package’s lack of stars/activity (0 stars, last release 2021) is a dealbreaker for your risk tolerance.

How to Pitch It (Stakeholders)

For Executives: "This package lets us automate audit logging—tracking user actions (logins, registrations) and system errors—without hiring engineers to build it. It’s a $0 cost (MIT license) and integrates seamlessly with Laravel, reducing our reliance on third-party tools. For example, we could use it to comply with GDPR by logging user consent changes, or debug production issues faster by centralizing errors in a searchable database table. The trade-off? We forgo real-time log streaming (which we don’t need yet) for a lightweight, scalable solution that scales with our team’s resources."

For Engineering: *"This is a drop-in Laravel logging solution that:

• Saves custom logs (e.g., LogFacade::generateLog("login")) to a database table with predefined types (configurable via log_types).
• Captures system errors automatically by extending Laravel’s ExceptionHandler (no manual log writing).
• Reduces technical debt by avoiding reinventing a logging wheel—it’s ~50 lines of code vs. a custom system.
• Low risk: The recent BaseFacade fix (v1.2.3) resolves a critical edge case, and it’s been stable since 2021. We’d need to:
  1. Publish the Blade menu (php artisan vendor:publish).
  2. Run migrations for the logs and error_logs tables.
  3. Define log types in config/log-manager.php. Downside: No active maintenance (last release 2021), but the codebase is simple enough to fork if needed. Alternatives like Sentry would add complexity and cost for our current needs."*