Xhprof Buggregator Bundle Laravel Package

Product Decisions This Supports

• Dev-experience / observability stack selection. Choosing whether Buggregator (a self-hosted, open-source server that aggregates XHProf profiles, dumps, Sentry events, Ray messages, Monolog logs, HTTP dumps, and mail) becomes the team's default local/staging debugging hub, versus paying for Blackfire or Tideways. This package is the "XHProf → Buggregator" adapter in that decision — one small piece of a broader tooling bet.
• Build vs. buy vs. vendor. The package is thin glue (a Symfony bundle that registers XHProf and ships profile payloads to a Buggregator endpoint). That makes it a legitimate "vendor it, don't depend on it" candidate: ~a few hundred lines you could own in-house in a sprint, with no license friction (MIT).
• Performance roadmap prioritization. Profiling data feeds the backlog: which endpoints, queries, or serializers are hot, whether an N+1 fix or a caching layer is worth the sprint, and where micro-optimization has no ROI. This is the input that turns "the app feels slow" into a ranked list.
• Production-readiness and capacity planning. Staging profiles under realistic load inform infra sizing and pre-launch performance gates, without paying for continuous production profiling on day one.
• Onboarding and DevEx standardization. A shared web UI for profiles lowers the barrier for new engineers versus reading raw xhprof_html output or hand-rolling profiler toggles in a dev container.
• Explicitly not a customer-facing feature. No user-visible capability, no revenue line, no SLA implication. Budget it as internal tooling with a fixed evaluation cost, not a platform commitment.
• Laravel caveat for the record: this is a Symfony bundle, not a Laravel package. If the roadmap is Laravel, the decision it informs is "which profiling path do we standardize on" — Telescope/Clockwork plus Xdebug, or Buggregator's own integrations — not "do we adopt this bundle."

When to Consider This Package

Adopt (as a timeboxed spike) when:

• You are on Symfony (not Laravel) with a Symfony version this bundle supports, and you can install the XHProf PECL extension in your dev/staging containers.
• You already run, or have already decided to run, a Buggregator server. Adopting this package in order to justify standing up Buggregator is backwards — evaluate the server first, the adapter second.
• More than one engineer needs to read profiles and share links, so the shared UI is worth more than the raw XHProf HTML reports.
• You are willing to pin the version, mirror the repository, or fork it internally.

Red flags to price in:

• 7 stars, 0 dependents, last release March 2024. Effectively a single-maintainer utility with no downstream proof. Treat it as unmaintained sample code, not a dependency with a support contract. Bus factor is the whole risk.
• Score 0.035 / opportunity 16.09 — low adoption signal; no ecosystem momentum to ride.

Look elsewhere when:

• You need production profiling at scale or continuous profiling — Blackfire, Tideways, Datadog/OTel continuous profiler are the right tools; sampling profilers in prod are a different product.
• You cannot install the XHProf PECL extension (shared hosting, locked-down images, or a preference for Xdebug) — the bundle has nothing to feed on.
• You need distributed tracing, not a flame graph from one request — evaluate OpenTelemetry instrumentation instead.
• You require vendor support, an SLA, or a security review trail — a 7-star MIT package will not clear procurement.
• You are on Laravel — this bundle is Symfony-only and will not wire into a Laravel service provider. The equivalent decision is Xdebug + Telescope/Clockwork, or Buggregator's own Laravel-side integrations.

How to Pitch It (Stakeholders)

To executives (one paragraph): This is a small, free, open-source adapter that lets our Symfony services send performance profiles into a self-hosted dashboard we would run ourselves. It removes the need for a per-seat profiling SaaS subscription during day-to-day development and gives us data to prioritize performance work. The trade-off: it is a low-adoption, single-maintainer project (7 stars, no dependents, last release March 2024), so we should treat it as a tactical tool — a one-sprint spike with a pinned version and a documented fallback — not a multi-year platform bet. Cost is near zero; the risk is maintenance, and it is contained.

To engineering: Adopt it only if we have already chosen Buggregator as our local debugging hub and can run XHProf in dev containers. It is thin glue — a bundle that registers XHProf and forwards profiles to Buggregator's UI — so plan to vendor or fork it rather than depend on upstream. Timebox the evaluation to one sprint, measure whether the shared UI actually changes how the team reasons about performance, and pre-agree the exit: Xdebug + Symfony Profiler, or Blackfire/Tideways if we need production-grade or supported profiling. Note for the Laravel teams: this package does not apply to you; your path is Telescope/Clockwork plus Xdebug, or Buggregator's own Laravel integrations.