Weave Code
Srf Datadog Statsd Bundle Laravel Package
mmz-srf/srf-datadog-statsd-bundle
A Symfony bundle for integrating Datadog StatsD metrics into PHP applications. It provides configuration and services to send counters, gauges, and timings, making it easier to instrument Symfony code and monitor application performance.
SRF Datadog StatsD Bundle provides a simple integration between Symfony/PHP applications and Datadog’s StatsD agent, making it easy to emit application metrics without boilerplate. Configure the agent connection once and inject a ready-to-use metrics service wherever you need counters, gauges, timings, or histograms.
- Configurable connection: set StatsD host, port, and metric namespace via bundle configuration.
- Service container integration: autowire a metrics client into services and controllers.
- Common metric types: counters, gauges, timers, and histograms.
- Environment-aware setup: use separate namespaces or endpoints per environment.
- Lightweight: a thin wrapper around Datadog StatsD with minimal overhead.
Frequently asked questions about Srf Datadog Statsd Bundle
- Is mmz-srf/srf-datadog-statsd-bundle a Laravel package?
- No. It is a Symfony bundle that registers through Symfony's Bundle class, DependencyInjection extension, and Configuration tree. Laravel's ServiceProvider, Facade, and config/*.php model does not consume those mechanisms. There is no supported bridge for loading Symfony bundles into a Laravel kernel.
- Can I install this Datadog StatsD bundle in a Laravel application?
- Composer resolution will almost certainly fail because the package targets Symfony 2.x and PHP 5.x era constraints. The last release was 2015-09-28 and the repository is archived. Forcing installation with --ignore-platform-reqs still leaves you with a stale 2015-era Datadog StatsD client API. It is not a reasonable dependency for a modern Laravel app.
- What is the recommended way to send Datadog StatsD metrics from Laravel?
- Reimplement the idea as a native Laravel service provider that binds a singleton of the current datadog/php-datadogstatsd client. Configure host, port, namespace, and global tags from config/datadog.php or config/services.php. Expose it through a thin facade or an injected MetricsClient interface. This is roughly half a day of work and gives you a dependency your team controls.
- Does this package support Laravel 8, 9, 10, or 11?
- No. The bundle targets the Symfony 2.x and PHP 5.x era and was archived after its 2015 release. Modern Laravel versions run PHP 8.x with Symfony 5 or 6 components. The Composer constraints conflict with the framework's locked dependency graph.
- Which Datadog StatsD client should I use with Laravel instead?
- Use the current datadog/php-datadogstatsd client and pin it in Composer. The 2015 client used by this bundle has different metric naming and lacks modern namespacing and tagging conventions. The modern client is the one Datadog documents and maintains. Verify PHP 8.x support on the exact version you choose.
- How do I configure Datadog StatsD host, port, namespace, and global tags in Laravel?
- Create a dedicated config/datadog.php file or add keys under config/services.php, reading values from environment variables. Register a singleton in a DatadogStatsdServiceProvider that resolves host, port, namespace, and global tags. Add a config flag to disable emission in local and test environments. Confirm UDP egress from web, queue workers, and the scheduler, and confirm the Datadog Agent is reachable in each environment.
- Is this bundle maintained or safe for production use?
- No. The repository is archived, has 2 stars, 0 dependents, and no upstream maintainer path for patches. There is no one to fix a CVE or a PHP 8 incompatibility. Forking it means inheriting a PHP 5-era codebase and permanently auditing it on every PHP or framework upgrade.
- How do I test Datadog StatsD metrics in Laravel without sending real metrics?
- Define a small MetricsClient interface and bind a null or in-memory implementation in your test suite. Add a config flag that disables emission in local and test environments. This keeps tests fast and deterministic. The interface also lets you swap to a DogStatsD sidecar or OpenTelemetry later without breaking callers.
- Will migrating away from this bundle break my existing Datadog dashboards?
- Only if the bundle's namespace and tag conventions were baked into dashboard queries. Port those metric names and tag strings verbatim into your new Laravel configuration. Instrument one pilot service first, then validate the dashboards before rolling out. Keeping the exact strings avoids breaking existing charts and alerts.
- What is the migration path from this Symfony bundle to native Laravel Datadog StatsD?
- Add and pin datadog/php-datadogstatsd, then create a DatadogStatsdServiceProvider with a singleton that reads host, port, namespace, and global tags from config. Define a MetricsClient interface with a test double and a config flag to disable emission locally. Instrument one pilot service deliberately, validate dashboards, and then roll out. Do not sequence this behind a port of the old bundle; the native provider is the lower-risk path.
Weaver
How can I help you explore Laravel packages today?