- Can I use intaro/pinba-bundle in a Laravel app?
- No. intaro/pinba-bundle is a Symfony bundle built around a Bundle class, DI compiler passes, and Symfony event subscribers, and those pieces have no direct Laravel analogue. A Laravel app should use the underlying Pinba PHP extension through a small first-party service provider and middleware instead.
- Is intaro/pinba-bundle a Laravel package?
- No, it is a Symfony bundle. Composer can install it, but Laravel will not load the bundle or its Symfony-specific integration points. Treat it as a reference implementation for Pinba timer lifecycle and tagging conventions, not as a dependency.
- How do I install intaro/pinba-bundle?
- In a Symfony project you install it with Composer, enable the bundle in the kernel, and configure the Pinba server host, port, and database. It is not a drop-in install for Laravel. Also confirm the pecl/pinba extension is available in the runtime before wiring the bundle.
- Does the Pinba PHP extension work on PHP 8.2?
- pecl/pinba has lagged PHP major releases, and PHP 8.x support depends on maintained forks or patches. You must verify a build against your exact PHP version before committing to Pinba. If no maintained build exists for your fleet, treat that as a hard blocker.
- Do I need a Pinba server and MySQL storage?
- Yes. Pinba uses a UDP collector plus a MySQL storage engine, so you must operate the daemon and plan retention and aggregation. The original Pinba project is effectively dormant and has friction with MySQL 8; the pinba2/pinba_server fork is the realistic target. Budget operational ownership, not just package installation.
- How do custom timers and tags work in Pinba?
- The bundle exposes Symfony services for starting and stopping timers and attaching tags, and underneath those calls map to procedural extension functions such as pinba_timer_start and pinba_timer_stop. In Laravel you would call the extension functions from your own wrapper or middleware and keep consistent naming conventions. Tags let you segment metrics by route, action, or other dimensions.
- What are the best alternatives to Pinba for Laravel monitoring?
- For local request inspection, Laravel Telescope and Debugbar are common. For production tracing and aggregate latency dashboards, OpenTelemetry-backed APM tools or Blackfire often require less custom infrastructure than Pinba. Pinba is strongest when you specifically want real-time per-request timers and custom tags in a Pinba server.
- Does intaro/pinba-bundle instrument Redis?
- No. The bundle includes Doctrine, Twig, and Memcache event subscribers, but it has no Redis instrumentation. Many Laravel stacks use Redis for cache, sessions, and queues, so that missing path can weaken the value proposition. Plan to add your own Redis timing hooks if that data matters.
- Is intaro/pinba-bundle actively maintained?
- Signals are weak: roughly 22 stars, zero dependents, and a single maintainer, which creates bus-factor risk. A reported last release date of 2026-06-09 looks like a metadata artifact, so verify composer.json and tag history before trusting release cadence. For a production bet, assume you may need to own fixes.
- How would a Laravel team build a Pinba integration?
- Start by validating the Pinba extension and server in a sandbox. Then build a small first-party package with a service provider that calls pinba_script_name_set, middleware for request timers, terminable middleware to flush on response, and a DB::listen hook for query timers. Keep it behind a config flag so Pinba is never a hard dependency of application boot.