Newrelic Bundle Laravel Package

Product Decisions This Supports

• Enhanced Observability Roadmap: Accelerates the rollout of a structured, Symfony-native observability layer by integrating New Relic seamlessly with transaction tracing, log correlation, and exclusion rules—reducing manual instrumentation effort.
• Build vs. Buy: Buy—avoids reinventing transaction naming, log batching, or exclusion logic, leveraging a battle-tested bundle (used by CHECK24, a DACH enterprise) instead of custom PHP/New Relic SDK work.
• Key Use Cases:
  • Microservices: Standardize transaction naming across Symfony services (e.g., API, CLI workers) with configurable strategies (e.g., route-based, command-based).
  • Log Correlation: Link logs to traces via traceId for debugging distributed systems (e.g., Messenger queues, async jobs).
  • Noise Reduction: Exclude non-critical transactions/exceptions (e.g., health checks, HttpExceptions) to declutter New Relic dashboards.
  • Performance Optimization: Batch logs (logging.buffer_size) to reduce overhead in high-throughput apps.

When to Consider This Package

• Adopt if:

  • Your stack is Symfony + PHP and you use New Relic for APM/logging.
  • You need automated transaction naming (e.g., for CLI commands, Messenger messages) without manual SDK calls.
  • Logs require trace correlation (e.g., for debugging async workflows).
  • You want to exclude specific routes/commands/exceptions from New Relic monitoring.
  • Your team lacks bandwidth to build custom New Relic integrations.

• Look elsewhere if:

  • You’re not using Symfony (this bundle is framework-specific).
  • You need advanced custom metrics (e.g., business KPIs) beyond transaction/logging—consider New Relic’s PHP agent or custom instrumentation.
  • Your app has extremely low/zero New Relic usage (overhead may not justify the bundle).
  • You require real-time data transmission (xmit: true)—this defaults to async for performance.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us automate 80% of New Relic setup for our Symfony apps—no more manual transaction naming or log correlation. CHECK24 (a DACH enterprise) uses it to monitor their high-traffic systems, and it’s MIT-licensed with recent updates. It’ll cut debugging time by linking logs to traces and filtering noise, while keeping our observability costs low by batching data. Minimal dev effort, big ROI for ops and reliability."

For Engineering: *"This replaces ad-hoc New Relic PHP agent tweaks with a Symfony-first solution:

• Transactions: Auto-names routes/commands (e.g., api.user_profile or messenger.send_email).
• Logs: Batches and correlates logs to traces via traceId—no more hunting for context.
• Exclusions: Skip irrelevant transactions (e.g., /health) or exceptions (e.g., HttpException) via config.
• Zero SDK boilerplate: Just install, configure, and go. Works with our existing New Relic license. Tradeoff: Async by default (configurable), but reduces latency vs. real-time xmit: true."*