Hibernate Laravel Package

Product Decisions This Supports

• Extensibility without forking (v1.9.3.4): custom monolog drivers mean we can route log/notification output to our own destinations (in-house audit store, data warehouse, SIEM, partner endpoints) while staying on the package's public API. This removes a recurring "fork it or wrap it" decision and lowers long-term maintenance cost.
• Build vs. buy: the package now covers the two most common asks we'd otherwise build ourselves — pluggable drivers and Slack delivery. Stronger case for buying/adopting rather than writing and owning a bespoke logging integration.
• Roadmap sequencing: Slack-over-webhook is a low-effort win to schedule now. Incoming-webhook delivery removes the need for a Slack app, OAuth scopes, and bot-token rotation, which typically unblocks security review and shortens time-to-value.
• Use cases unlocked: dev/staging alert fan-out to Slack with a single URL per channel; multi-tenant or per-customer log routing via custom drivers; migration path off legacy token-based Slack integration without changing application code.
• Risk reduction: no breaking changes flagged, so adoption can proceed incrementally per environment (start with non-production webhook channels, then production).

When to Consider This Package

Consider adoption when:

• We need log/notification delivery to be configurable per environment or per tenant, and we don't want driver selection hardcoded in application code.
• Security or IT has objections to storing Slack bot tokens (rotation burden, scope creep, secret sprawl). Webhook URLs are narrower and easier to scope per channel.
• We already send alerts to Slack and want channel-per-team routing without building a Slack app.
• We anticipate a custom sink (SIEM, S3, internal event bus) within the next 1–2 quarters — this release is the hook we'd otherwise have to build.
• We want to reduce bespoke integration code in our Laravel services.

Look elsewhere or defer when:

• Our needs are strictly single-destination, single-tenant logging with no customization — a native Laravel logging channel may be sufficient.
• Compliance requires fully managed, vendor-supported log pipelines with SLAs; a community package adds ownership we may not want.
• We require guaranteed delivery/retry semantics or schema contracts — verify this (and the custom-driver contract's stability) before committing.
• Webhook-only Slack is a blocker for interactive features (buttons, modals, slash commands) that need a full Slack app.

How to Pitch It (Stakeholders)

For executives: A low-risk maintenance release that removes two blockers we'd otherwise pay to solve. It lets us plug our own log destinations in without forking a third-party library, and it lets us wire Slack alerts using simple webhooks instead of app credentials — cutting security review time and token-rotation overhead. No breaking changes; value is available without a migration project.

For engineering: Two incremental capabilities. (1) Custom monolog drivers are now supported, so we can register internal handlers as first-class drivers and configure them like any built-in channel — no wrappers, no patches. (2) Slack can authenticate via incoming webhook rather than a bot token, which simplifies secrets management and lets us map one webhook per channel/team. Recommended next step: a time-boxed spike registering one custom driver against a non-production sink, and a webhook-based Slack channel in staging. Track the custom-driver interface as a public-contract surface and pin the minor version until we've validated it.