- Can I install liuggio/statsd-client-bundle in Laravel?
- Direct installation is not practical. This is a Symfony2 bundle built around Symfony's dependency injection container, bundle configuration, and event system, while Laravel uses service providers, facades, and its own config layer. Modern Laravel also requires PHP 8.0 or newer, and the bundle's legacy Symfony 2.x and PHP 5.5 to 7.x constraints will likely make Composer block installation.
- Does liuggio/statsd-client-bundle support Laravel 9, 10, or 11?
- No. The bundle targets Symfony 2.x and PHP 5.5 to 7.x-era runtimes, while Laravel 9, 10, and 11 require PHP 8.0 or newer. Its last release was in February 2016 and it is not maintained, so Composer constraints and missing PHP 8 compatibility will prevent a clean install.
- What metrics can I send with this StatsD bundle?
- The bundle exposes the StatsD PHP client through Symfony services so applications can emit counters, timers, gauges, and sets over UDP. It supports configurable StatsD servers, a metric namespace, and UDP transport, with fire-and-forget collection meant for lightweight instrumentation. In Laravel, you would need to extract or wrap the underlying client rather than use the bundle.
- Is liuggio/statsd-client-bundle maintained?
- It is effectively abandoned. The last release was 2016-02-25, it has zero dependents, and there is no active maintenance or security patching. Symfony 2.x is end-of-life, so using it introduces technical debt and upgrade blockers; if you fork it, your team owns maintenance.
- How do I use StatsD in Laravel instead?
- Select a maintained Laravel-native or framework-agnostic StatsD client instead. Bind the client as a singleton in a Laravel service provider, read host, port, and namespace values from config or environment variables, and inject it into controllers, services, or console commands. Test emission against a non-production StatsD daemon before relying on the metrics. Avoid pulling the Symfony2 bundle into Laravel.
- Can I extract the underlying liuggio/statsd-php-client and use it in Laravel?
- It may be possible, but only as a short spike. The underlying liuggio/statsd-php-client library is likely more framework-agnostic than the bundle, while the bundle itself adds Symfony-specific wiring that does not map to Laravel. Extract the client, verify PHP 8 compatibility, wrap it in a Laravel service provider, and test the metrics you actually need. Compare that effort against a maintained alternative first.
- What PHP and Symfony versions does this bundle require?
- The bundle requires Symfony 2.x and PHP from roughly the 5.5 to 7.x era. Those constraints conflict with modern Laravel applications that require PHP 8.0 or newer. Expect Composer dependency conflicts and no security patches for the legacy stack.
- Does this bundle work with PHP 8 or modern Laravel?
- No. It targets PHP 5.5 and 7.0-era runtimes and Symfony 2.x, so PHP 8 and modern Laravel are outside its supported stack. In practice you should expect Composer resolution failures or fatal compatibility errors. Do not use it in production for a current Laravel application.
- What are alternatives to StatsDClientBundle for Laravel?
- Use a maintained StatsD client such as league/statsd or a Laravel-specific metrics package, or wrap the underlying liuggio/statsd-php-client in your own service provider if you must reuse it. Check whether you need counters, timers, gauges, sets, tags, or histograms before choosing. Skip the abandoned Symfony2 bundle and align the choice with your observability roadmap.
- Is StatsD over UDP reliable for production Laravel metrics?
- StatsD over UDP is fire-and-forget, so metrics can be silently dropped under load or network issues. The lightweight client itself is not the scaling concern; the StatsD daemon and backend determine reliability and retention. With this bundle, legacy configuration and Symfony container errors add risk, and a custom Laravel adapter increases misconfiguration risk. Monitor emission and test failover behavior before trusting the data.