Laravel Elastica Bridge Laravel Package

Product Decisions This Supports

• Feature/roadmap: v2.2.0 adds a configurable minimum log level for Sentry breadcrumbs via elastica-bridge.logging.level / ELASTICSEARCH_LOG_LEVEL, with a safe default of debug.
• Operational cost control: Teams can raise the breadcrumb log level in production to reduce memory use when sentry_breadcrumbs is enabled, since Elasticsearch logs full request and response bodies at debug.
• Environment-specific configuration: Supports differentiated logging policy across local, staging, and production without code changes.
• Incident diagnostics vs. overhead trade-off: Product/engineering can decide how much Elasticsearch request/response detail to attach to Sentry breadcrumbs based on debugging needs and memory constraints.
• Low-risk adoption: Default behavior is unchanged unless the new setting is explicitly configured, so this is a non-breaking feature release suitable for normal upgrade planning.
• Build vs. buy: If the package already provides the Elasticsearch/Sentry integration, this is a small configuration-level improvement rather than a reason to build custom observability plumbing.

When to Consider This Package

• Consider it when a Laravel/PHP product uses Elasticsearch and Sentry together, especially if Sentry breadcrumbs are enabled in environments where Elasticsearch request/response logging may increase memory usage.
• Strong fit when teams want package-level configuration for logging verbosity rather than custom application code or environment-specific patches.
• Useful when production observability needs to balance diagnostic detail against runtime overhead and cost.
• Look elsewhere if the product does not use Elasticsearch, does not use Sentry breadcrumbs, or needs advanced log sampling, redaction, retention, or observability policy beyond a minimum log level.
• Reassess if the package lacks broader maintenance, documentation, or compatibility guarantees needed for production; this release note alone does not establish those.

How to Pitch It (Stakeholders)

v2.2.0 is a low-risk, configuration-only feature for teams using this Laravel/PHP package with Elasticsearch and Sentry. It lets us raise the minimum log level for Sentry breadcrumbs in production to reduce memory use when full Elasticsearch request/response logging at debug is unnecessary. Because the default remains debug, existing behavior does not change unless we opt in. For engineering, this is a simple operational lever; for executives, it supports safer production observability with lower memory pressure and no forced migration.