Weave Code
Datadog Symfony Laravel Package
okvpn/datadog-symfony
Symfony bundle for Datadog observability. Configure DogStatsD metrics, APM tracing, and event/log forwarding from your Symfony app, with container integration and environment-based settings for production monitoring.
:dog: Symfony Datadog integration
Frequently asked questions about Datadog Symfony
- Does okvpn/datadog-symfony work with Laravel?
- This is a Symfony bundle, not a Laravel package, and the release notes do not describe a Laravel service provider. To use it in Laravel you would bridge the underlying DogStatsD client through your own service provider or use the client directly while adopting the DSN conventions. Prove the container wiring in a spike before committing, because Symfony service IDs and compiler passes do not map one-to-one to Laravel's container.
- How do I install okvpn/datadog-symfony with Composer?
- Install it with composer require okvpn/datadog-symfony. In Symfony you register the bundle and configure the clients map under the bundle's config key. In Laravel, installation is only the first step because container integration is not provided out of the box.
- How do I configure Datadog DogStatsD DSNs for multiple clients?
- Version 1.0 appears to replace the single-DSN settings with a clients map keyed by name, where each value is a DSN string. The scheme encodes transport host and port, with the namespace as a path segment and default tags as a comma-delimited query value. The default client key appears significant for default-client resolution, so keep it stable and drive DSNs from environment variables per environment.
- Can I use null:// and mock:// DSNs for testing?
- Yes, multi-client support makes null:// and mock:// first-class sinks. null:// disables emission, while mock:// is intended to capture metrics for assertions so you can test without a Datadog Agent. Confirm in a spike that mock:// exposes a retrievable metric buffer suitable for your CI assertions.
- What PHP and Symfony versions does okvpn/datadog-symfony 1.0 require?
- The 1.0 release adds Symfony 7.0 support, which implies PHP 8.2 or newer. If your Laravel app pulls Symfony components such as console or http-foundation transitively, verify Composer resolves those constraints alongside your PHP 8.2/8.3 CI and production versions. The framework mismatch remains the main risk for non-Symfony containers.
- How do I migrate from 0.x to 1.0 of okvpn/datadog-symfony?
- The main breaking change is configuration: the single-DSN settings appear replaced by a clients map, and service IDs plus default-client resolution must be re-verified. Migration notes are absent in the release, so inventory every config key and call site that fetches a client. Translate them to the named clients map, then diff emitted metric names and namespaces before and after using a mock sink.
- How do DSN default tags combine with per-call tags?
- Default tags are supplied in the DSN query string as a comma-delimited value, while per-call tags are passed by application code. The merge order between client defaults and per-call tags is unspecified in the release notes. Test whether per-call tags override or append before relying on them for routing or cost attribution.
- Is UDP DogStatsD reliable enough for production metrics?
- DogStatsD over UDP is fire-and-forget and has no delivery guarantee, so failures are silent by design. Make sure the Datadog Agent 7.x is reachable via sidecar, DaemonSet, or localhost on UDP 8125, and monitor agent health separately. For critical metrics, consider an agentless API path or a fallback pipeline.
- Are there Laravel alternatives to okvpn/datadog-symfony?
- The underlying concept is a thin, configuration-driven DogStatsD emitter, and you can adopt the DSN model without the Symfony bundle. Alternatives include dedicated Laravel Datadog packages or a small custom service provider around a DogStatsD client. Choose based on whether you need the bundle's multi-client and mock sink features or just simple counters and timings.
- Is okvpn/datadog-symfony actively maintained?
- The 1.0 release signals a stable major with Symfony 7 support and multi-client configuration. Maintainer cadence and support model are not stated in the release notes, so check repository activity before adopting. Have a fallback plan, such as wrapping the underlying client directly, if maintenance stalls.
Weaver
How can I help you explore Laravel packages today?