Weave Code
Actuator Doctrine Bundle Laravel Package
symsensor/actuator-doctrine-bundle
Symfony bundle that adds Doctrine ORM health checks and diagnostics to symsensor/actuator, exposing entity manager status, database connection health, and schema information through actuator endpoints for monitoring Symfony applications.
Symsensor Actuator Doctrine Bundle integrates Doctrine connectivity checks into Symfony’s Actuator health endpoints. It helps monitor database availability and surface Doctrine-related status through a consistent, configurable health-reporting interface.
- Exposes Doctrine connection health as an Actuator indicator
- Detects database connectivity failures early
- Pluggable into existing Symfony Actuator setups
- Configurable checks for different environments
- Lightweight bundle with minimal configuration
Frequently asked questions about Actuator Doctrine Bundle
- Can I install symsensor/actuator-doctrine-bundle directly in a Laravel application?
- Not realistically. It is a Symfony bundle that expects Symfony bundle registration, DI configuration, and ActuatorBundle extension points, while Laravel uses service providers and a different config and routing model. A direct Composer install would not wire up health endpoints or Doctrine checks without a compatibility layer or fork.
- Does this package support Laravel 10 or Laravel 11?
- There is no stated Laravel support. The package targets Symfony and Doctrine through ActuatorBundle, and its PHP, Symfony, Doctrine, and ActuatorBundle constraints are not summarized in the provided context. Treat Laravel 10 or 11 compatibility as unverified and require a dependency and source review before any spike.
- What does the Doctrine health check actually report?
- The overview says it exposes database connectivity checks, connection and entity manager status, and query insights, but the exact response schema is not documented here. Confirm whether an endpoint returns a simple boolean, latency, replica status, or detailed connection data. That matters because richer responses can leak database availability or connection details.
- How are multiple Doctrine connections handled by this bundle?
- The provided context does not specify how multiple Doctrine connections are selected or reported. You would need to inspect the bundle source and configuration to see whether it checks a default connection, all configured connections, or supports explicit selection. For Laravel, any fork should define connection selection clearly in its health-check contract.
- Is there a native Laravel alternative to this Symfony Doctrine health check?
- Yes, for most Laravel apps a native health check is simpler and lower risk. You can test the default database with DB::connection()->getPdo() or a lightweight query, and use Laravel’s scheduling, middleware, and routing for the endpoint. If the app uses Doctrine inside Laravel, check the Doctrine connection directly rather than adopting a Symfony bundle.
- How should I secure the Doctrine actuator health endpoint in production?
- Do not expose database health details publicly by default. Put the endpoint behind authentication, network restrictions, or an internal monitoring route, and define timeout and failure behavior so degraded databases do not hang requests. Also review error disclosure because connection failures can reveal host, driver, or credential-adjacent information.
- Does symsensor/actuator-doctrine-bundle require Doctrine ORM or only DBAL?
- The package description mentions Doctrine connections and entity manager status, which implies ORM awareness, but the exact DBAL versus ORM requirement is not confirmed in the provided context. Inspect composer.json and the bundle extension to verify the dependency chain. If you only need connection availability, a DBAL-only check may be enough and simpler to implement natively.
- What PHP, Symfony, and Doctrine versions does this bundle support?
- The provided evaluation says the version constraints are unknown without inspection. The last release was December 2023, so test against your current PHP, Symfony components, Doctrine DBAL or ORM, and ActuatorBundle versions. Do not assume compatibility with the latest Symfony or Doctrine releases.
- Is this package actively maintained and safe for production use?
- Community validation is very low: zero stars, zero dependents, and a last release in December 2023. That does not prove the code is unsafe, but it means you should expect to own fixes and security review if you adopt it. For a Laravel app, the maintenance burden of a fork likely outweighs the value of a small health-check feature.
- How would I port this Symfony bundle to Laravel?
- Use it as a reference implementation rather than forcing Symfony bundle registration into Laravel. Define the endpoint path, response schema, authentication, timeout semantics, and connection selection, then implement a Laravel service provider, config file, route or controller, and health-check service. Isolate the port in an internal package with tests and document the response contract before canary deployment.
Weaver
How can I help you explore Laravel packages today?