Laravel Contextify Laravel Package

Product Decisions This Supports

• Staged rollout and reversibility of observability work. 4.4.0 adds a config flag to fully disable Contextify. That turns context propagation from a "ship it and live with it" dependency into something you can gate per environment. PM-relevant decisions this unblocks: enable in staging and production, disable in local/CI to keep test output and logs readable, and flip it off in production as a first-response mitigation if the middleware is implicated in latency or log-volume issues — without a code revert or a deploy.
• Build vs. buy for request context. If the roadmap includes correlation IDs, trace/request IDs, or user context threaded through logs, queued jobs, and outbound HTTP calls, this package is the "buy" option against a bespoke middleware + log processor + queue-payload decorator you'd otherwise own and maintain.
• Incident response and MTTR as a product commitment. Being able to turn context propagation on/off by config makes it easier to argue for adopting it as part of the standard service template rather than a per-team choice.
• Environment-tiering decisions. One config surface for "on in prod, off in CI" means you can adopt the package in composer.json for all environments while only activating it where it earns its keep.
• Scope boundaries for observability spend. Because the disable switch exists, this package can be the low-cost default while a full tracing/APM decision is deferred — a useful way to keep an observability initiative moving without committing to a vendor.

When to Consider This Package

Consider adopting when:

• You have a Laravel application (or several) where logs, queued jobs, and outbound HTTP calls currently lack a shared correlation identifier.
• You want context propagation as configuration rather than a maintained internal package — the new kill switch is exactly the kind of operational lever that makes a community dependency defensible.
• You need environment-specific behavior (verbose locally, silent in CI, active in production) and don't want conditional code in your service providers.
• You're standardizing a service template and want a dependency that can be adopted by default and disabled per-service if it misbehaves.

Look elsewhere when:

• You already run OpenTelemetry, a full APM agent, or a logging platform that injects and propagates context itself — you'd be duplicating a solved problem.
• You need vendor-neutral, cross-language tracing semantics; a Laravel-specific package won't cover non-PHP services in your estate.
• The application is a small monolith with a single log sink and no async work; the payoff is thin.
• You require a formal support contract, published SLA, or an auditable security review process that a single-maintainer package can't provide. The 4.4.0 config flag is reassuring for operations, but it doesn't change the governance math.

How to Pitch It (Stakeholders)

For executives: This is a small, reversible dependency that improves our ability to diagnose production issues. The 4.4.0 release makes it switchable by configuration, so we can adopt it broadly, roll it out environment by environment, and turn it off in seconds if it causes trouble — no emergency deploy. It reduces mean time to resolution for incident work and avoids us building and maintaining an equivalent internal utility. Cost is one Composer dependency.

For engineering: Contextify threads request context through logs, jobs, and HTTP clients via middleware. 4.4.0 adds a config option to disable it entirely, which is the practical unlock: keep it installed everywhere, enable it in staging/production, and leave it off in local and CI so test output stays clean. There's no API break in this release — it's an additive config flag — so adoption is a config change plus a composer update, and the off switch gives you a clean rollback path if you see unexpected log volume or middleware overhead. Recommended next step: enable in one staging service, confirm log correlation and job propagation behave, then promote via the service template.