- Does ozznest/apm-bundle work with Laravel?
- No. Despite being described as suitable for Laravel/PHP applications, ozznest/apm-bundle is a Symfony bundle registered through the Symfony kernel, dependency injection container, and event dispatcher. Laravel has no bundle loader, no container compilation passes, and no kernel event subscribers, so none of the package's auto-instrumentation hooks fire. Making it work would require a custom adapter that fakes a Symfony runtime inside Laravel, which is bespoke code you would own indefinitely.
- How do I install ozznest/apm-bundle in a Laravel application?
- You cannot install it as a normal Laravel package. There is no service provider, no publishable config, and no middleware, so adding it to composer.json gives you an unregistered bundle that does nothing. A working install would need a hand-written service provider, a translation layer between Laravel's middleware and terminable middleware lifecycle and Symfony's request/response events, plus manual registration of any collectors the bundle would otherwise auto-discover. That effort is not justified by the package's remaining value.
- Which Laravel and PHP versions does ozznest/apm-bundle support?
- Laravel is not a supported target at all, so there is no Laravel 10, 11, or 12 test matrix. The last release was published on 2022-01-04, which predates current PHP 8.3 and 8.4 validation and means the declared Symfony and PHP version constraints are likely to conflict with a modern dependency tree. Check the composer.json constraints on the repository before planning any spike, because a failed resolution ends the evaluation immediately.
- Is ozznest/apm-bundle still maintained?
- There is no meaningful maintenance signal. The project shows zero stars and zero dependents on the repository, and the most recent release is dated 2022-01-04, roughly three years stale. Zero adoption also means no CVE response path and no community pressure to fix compatibility breaks. Treat it as a dormant personal project until a named maintainer and release cadence can be confirmed.
- What does ozznest/apm-bundle actually monitor?
- The stated scope is lightweight performance monitoring for requests, database queries, exceptions, and slow endpoints. The stated goal is minimal-configuration instrumentation so you can spot bottlenecks without wiring up collectors by hand. What the evaluation could not confirm is which APM backend receives that data, so verify whether it emits to a vendor agent, an OTLP endpoint, or a proprietary collector before assuming any telemetry will be usable.
- How do I configure ozznest/apm-bundle for a Laravel app?
- The bundle exposes a Symfony configuration tree loaded through its DI extension, which does not map onto Laravel's config files without manual flattening. You would have to confirm the tree can be expressed flatly enough for a config/apm.php file and then hand-bind those values into the container yourself. In practice the configuration surface is only worth porting if you have already decided to keep the underlying SDK.
- What are the best alternatives to ozznest/apm-bundle for Laravel?
- Use a maintained option instead: the OpenTelemetry PHP SDK with Laravel auto-instrumentation, or a vendor agent such as Datadog, New Relic, Sentry Performance, or Scout. These give you a supported PHP version matrix, an active security response path, and instrumentation built for Laravel's actual lifecycle. Replacing the bundle is the recommended path in roughly ninety percent of cases.
- Can I skip the bundle and use the underlying APM SDK directly?
- That is a genuinely good question and one the repository does not clearly answer. If the bundle is a thin Symfony wrapper over a still-maintained APM client, consuming that client directly in Laravel salvages the useful part and discards the Symfony coupling. Confirm whether an independent SDK package exists and is maintained before spending time on any adapter work.
- How do I test that this APM instrumentation is actually reporting in production?
- An APM agent that fails silently is worse than no agent, because you lose telemetry without knowing it. Build an explicit verification step that asserts spans or transactions arrive at the backend after a test deploy, rather than trusting that installation succeeded. Given the package's age and unverified backend, run any spike in a throwaway Laravel or Symfony application first and confirm end-to-end delivery before touching production.
- Is ozznest/apm-bundle safe and licensed for production use?
- The evaluation could not confirm maintainer identity, license terms, or whether the underlying APM SDK is a vendored or forked dependency, so supply-chain risk is unknown. Before any code is written, verify the license permits internal forking and redistribution, check for abandoned transitive dependencies, and confirm PSR-3/PSR-4 compliance. Fork and adapt only if a specific capability here is truly unavailable elsewhere, and only with a named owner and a maintenance budget.