Tactician Logger Laravel Package

Product Decisions This Supports

• Debugging & Observability: Enables structured logging of command bus interactions (e.g., command dispatch, handler execution, errors) to improve debugging and troubleshooting in production/non-production environments.
• Audit Trails: Facilitates compliance or audit requirements by logging command payloads, timestamps, and outcomes (success/failure) for critical workflows (e.g., payments, user actions).
• Performance Insights: Logs execution times for commands/handlers to identify bottlenecks in asynchronous workflows (e.g., background jobs, event-driven systems).
• Build vs. Buy: Justifies buy for teams already using Tactician (League’s command bus) or PSR-3 loggers (e.g., Monolog, Symfony Logger), avoiding custom logging middleware development.
• Roadmap Prioritization: Supports scaling complex command buses (e.g., microservices, event sourcing) where visibility into command flow is critical.
• Error Handling: Reduces MTTR by logging exceptions/errors with context (e.g., command payload, handler class) for faster incident response.

When to Consider This Package

• Use This When:

  • Your application uses Tactician (League’s command bus) and lacks centralized logging for command execution.
  • You need PSR-3 compliant logging (e.g., Monolog, AWS CloudWatch, Datadog) to track command bus activity.
  • Debugging asynchronous workflows (e.g., queues, cron jobs) requires visibility into command lifecycle.
  • Compliance/audit requirements mandate logging of command payloads, timestamps, or outcomes.
  • You’re evaluating observability tools (e.g., ELK, Splunk) and need structured logs for command buses.

• Look Elsewhere If:

  • You’re not using Tactician: This package is a plugin for Tactician only; alternatives like Laravel’s built-in logging or custom middleware may suffice.
  • Your logging needs are basic (e.g., only logging errors) and don’t require command-level granularity.
  • You’re using a non-PSR-3 logger (e.g., proprietary logging systems) without PSR-3 adapters.
  • Your team lacks PHP/Laravel expertise to integrate plugins (low-code/no-code teams may prefer built-in solutions).

How to Pitch It (Stakeholders)

For Executives:

*"This lightweight package adds real-time visibility into our command bus workflows—critical for debugging, auditing, and performance tuning. By logging every command (e.g., payments, user actions) with timestamps and outcomes, we can:

• Reduce downtime by quickly identifying failed commands in production.
• Meet compliance requirements with structured logs of sensitive operations.
• Avoid reinventing the wheel: It’s a 5-minute setup for teams already using Tactician, saving dev time vs. custom logging. Cost: Free (MIT license), ROI: Faster incident response, better audit trails."*

For Engineers:

*"tactician-logger is a zero-boilerplate way to log Tactician commands using PSR-3 (e.g., Monolog). Key benefits:

• Plug-and-play: Works with existing Tactician setups; just add the plugin and configure your logger.
• Rich context: Logs include command payloads, handler execution time, and errors—ideal for debugging async workflows.
• Flexible: Supports any PSR-3 logger (e.g., Symfony, AWS CloudWatch). Tradeoff: Minimal overhead (~10ms per command for logging); worth it for observability. Alternatives: Custom middleware (higher maintenance) or Tactician’s built-in logging (less structured)."*

For DevOps/SRE:

*"This package standardizes command bus logging, making it easier to:

• Correlate logs with other services (e.g., queues, databases) using command IDs.
• Alert on failures (e.g., failed payment commands) via log aggregation tools (ELK, Datadog).
• Retain audit trails for compliance (e.g., GDPR, financial transactions). Setup: Configure once in tactician.php; logs appear in your existing PSR-3 pipeline. Note: Ensure log retention policies align with your compliance needs."*