- What is Larametrics and what does it do?
- Larametrics is a self-hosted metrics and notifications platform for Laravel applications. It tracks requests, model events, and custom metrics in a built-in dashboard, then sends email or Slack notifications when errors occur or thresholds are crossed. It is intended as an internal operational dashboard or lightweight alerting layer rather than a customer-facing dependency.
- How do I install Larametrics in a Laravel app?
- Installation is typically done through Composer using the aschmelyun/larametrics package, followed by publishing configuration, running migrations, and wiring up the dashboard and notification settings. Because the package is archived and was last released in January 2020, you should prove compatibility on your current Laravel and PHP versions before adding it to a production app. Start in a disposable app or branch and pin the package and its transitive dependencies.
- Which Laravel and PHP versions does Larametrics support?
- The provided context does not list explicit Laravel or PHP version constraints, so support must be verified from the package's Composer metadata and a compatibility spike. The package was last released in January 2020 and is archived, meaning modern Laravel and PHP compatibility should not be assumed. Check framework constraints, package discovery, Symfony components, database drivers, and migration behavior on your target stack.
- Is Larametrics still maintained?
- No, the evaluation states that Larametrics is archived and was last released in January 2020. That means no upstream security fixes, Laravel upgrade support, dependency maintenance, or bug resolution from the original project. It also has zero dependents, which gives little ecosystem evidence of current production use.
- How does Larametrics handle authentication for its dashboard?
- The dashboard is a key security concern because it exposes metrics and potentially operational data inside your Laravel app. The evaluation recommends isolating it as an internal tool or admin-only module behind a dedicated guard and feature flag. You should perform a security review of dashboard access and ensure it is not publicly reachable.
- Can Larametrics send alerts to Slack and email?
- Yes, the package description says it can notify via email or Slack when errors occur or thresholds are crossed. In practice, you need to validate the mail and queue drivers your app uses and review how notification credentials are stored. Treat notification credential handling as part of your security review before production use.
- Does Larametrics require database migrations or scheduled jobs?
- The technical evaluation indicates that Larametrics likely introduces routes, views, configuration, migrations, scheduled collection, and notification plumbing. That means you should expect schema changes and operational setup rather than a drop-in library. Confirm the exact requirements during a compatibility spike and test migrations against your target database.
- How do I track custom metrics and model events with Larametrics?
- Larametrics is described as tracking requests, model events, and custom metrics in its built-in dashboard. The exact APIs and configuration for custom metrics should be verified from the package source and README during your spike. Avoid embedding collection calls in critical request paths until stability is proven.
- Can I fork Larametrics and maintain it internally?
- The MIT license allows an internal fork, but doing so converts the package into an owned platform with ongoing maintenance cost. If the compatibility spike passes, fork it into an internal namespace, add tests, update dependency constraints, and document a clear owner. If it fails, the evaluation recommends evaluating a maintained observability stack instead of patching in place.
- What are alternatives to Larametrics for Laravel monitoring?
- Alternatives include OpenTelemetry, Prometheus with Grafana, Sentry, and managed observability services. Larametrics makes sense only if your team explicitly wants self-hosted metrics and alerting inside a Laravel-centric app. Teams already standardized on an external observability stack should probably not adopt an archived package for this role.