- What is mantas-done/laravel-apm used for?
- It is a lightweight, self-hosted application monitoring package for Laravel. It captures requests, database queries, jobs, and exceptions so developers can review performance data in a simple dashboard and find slow endpoints or bottlenecks. It is positioned as an alternative to sending telemetry to an external monitoring service.
- How do I install mantas-done/laravel-apm in a Laravel application?
- The expected integration path is Composer-based, followed by Laravel service-provider registration, configuration publishing, middleware setup, and database migrations. The TPM assessment recommends piloting this in a non-production environment first, running migrations against a disposable database, and validating dashboard data quality. Confirm the exact install commands and required Laravel bootstrapping steps in the package documentation for your version.
- Which Laravel and PHP versions does laravel-apm support?
- The provided context does not list specific Laravel or PHP version constraints, so you should check the package composer.json and README before adopting it. The TPM assessment specifically flags supported Laravel and PHP versions as a key question to confirm. Because the last release date noted is 2024-02-07, run an explicit compatibility test against your target Laravel and PHP runtime.
- What storage backend does laravel-apm require and how is retention handled?
- The assessment points to relational storage, configuration publishing, and database migrations, but the exact required backend should be confirmed in the package docs. Retention behavior is important because telemetry can increase database size and write pressure. Define a retention policy and test storage growth before enabling it broadly in production.
- Does laravel-apm capture database queries, jobs, exceptions, and scheduled tasks?
- The package overview explicitly names requests, database queries, jobs, and exceptions. The TPM assessment also lists scheduled tasks and outgoing HTTP calls as items to verify, so do not assume those are covered without checking the documentation for your version. Validate the exact instrumentation you need in staging before relying on it for operations.
- What is the production overhead of using laravel-apm?
- It is described as lightweight, but the assessment warns that telemetry volume and database write pressure are the main scaling risks. You should run a staging load test against a baseline and enable sampling or retention limits where appropriate. Measure request overhead and database growth with representative traffic before a production canary.
- How does laravel-apm handle PII and sensitive query parameters?
- The package overview does not promise automatic redaction of personal data or sensitive query parameters. Treat captured request, query, job, and exception data as potentially sensitive and review the configuration and documentation for redaction options. Before production use, restrict what is captured, enable sampling if needed, and confirm how telemetry data is stored and accessed.
- Does laravel-apm work with Laravel Octane, Horizon, and queue workers?
- The TPM assessment calls out Octane, Horizon, queue workers, and read/write database splits as compatibility items to validate. Job capture suggests queue-worker relevance, but you should not assume full support without testing your deployment model. Run compatibility checks in staging, especially if you use long-running workers or Octane.
- Is mantas-done/laravel-apm actively maintained and what support is available?
- At assessment time the repository had 59 GitHub stars and a last release dated 2024-02-07, with MIT licensing and community-only support. That low adoption and stale release cadence increase dependency-compatibility and long-term ownership risk. For business-critical use, monitor advisories and plan a maintained fork or replacement path.
- How can I roll back or remove laravel-apm from production?
- A safe rollback starts by disabling the package middleware and service provider, then stopping telemetry writes so the application no longer records data. After that, remove or archive the package tables and published configuration according to your database and deployment procedures. Test the rollback in staging first and document it before enabling the package in production.