- Can I use presta/datadog-bundle in a Laravel app?
- No. It is a Symfony bundle registered through bundles.php and Symfony's DI container and config-tree conventions, and Laravel has no equivalent extension point. A Laravel application cannot consume its intended surface at all. Treat the package as a code sample, not a dependency.
- What does PrestaDatadogBundle actually do?
- It is a thin Symfony configuration shim that wires a Monolog handler to ship log records to Datadog's HTTP log intake. The durable value is roughly 50 to 100 lines of handler plus DI configuration; the rest is convention. It provides no Laravel service provider or Laravel logging channel.
- Does presta/datadog-bundle support Monolog 3 and Symfony 6.4 or 7?
- Probably not. The last release was February 2023, so it likely caps at Monolog 2.x and Symfony 5 or 6, and Monolog 3 changed handler constructor signatures. Verify the composer.json constraints and run a dry install against your current lockfile before committing.
- How do I send Laravel logs to Datadog without this package?
- Emit structured JSON via a JsonFormatter to stdout or a file channel, then ship with the Datadog Agent or Fluent Bit. Keep a single outbound HTTP handler as a documented fallback for hosts where the Agent cannot run. This decouples logging from the vendor and gives you buffering, retries, and disk-backed queuing for free.
- How can I reuse the Datadog Monolog handler in my Laravel project?
- The handler class is small and MIT-licensed, so copy it into app/Logging/ with an attribution header. Wire it through Log::extend or a custom channel in config/logging.php, then remove the Composer dependency. That fork-and-own path is a one-afternoon job and the only one recommended for a Laravel codebase.
- Is presta/datadog-bundle maintained and safe for production?
- There is no meaningful maintenance signal: 0 stars, 0 dependents, and a single release from February 2023. There is no security response path, so your team becomes the effective maintainer. Do not adopt it as a dependency; vendor the handler if you need the code.
- What security risks come with a Datadog log handler?
- Datadog intake handlers authenticate with a client token embedded in the request, so misconfiguration can leak the token itself. Naive context or exception formatting can also forward application payloads into log output. Read the handler before trusting it, and scrub or whitelist context rather than forwarding the record wholesale.
- Does the bundle's Monolog handler batch or buffer log records?
- The available context points to synchronous per-record HTTP on the request path, which is a latency and backpressure hazard under load. Confirm in the handler whether it buffers, batches, or silently drops records. If it does not, prefer the Datadog Agent or sidecar for buffering, retries, and disk-backed queuing.
- What Datadog source, tags, and env conventions does it encode?
- The bundle encodes Datadog source, tag, and env conventions through its config tree, but the excerpt does not specify the exact values. Read the configuration and handler to see what it sets, then compare that with your existing Datadog taxonomy. If they do not match, a custom handler gives you full control.
- What are the alternatives to presta/datadog-bundle for Datadog in PHP?
- Use the Datadog Agent or sidecar consuming structured JSON from stdout, or point Monolog's stock CurlHandler or HttpHandler at http-intake.logs.datadoghq.com. For APM tracing, use datadog/dd-trace. The bundle adds little over these options unless you specifically need its Symfony wiring.