Weave Code
Laravel Newrelic Laravel Package
intouch/laravel-newrelic
intouch/laravel-newrelic integrates New Relic APM with Laravel, providing transaction, exception, query, and job monitoring out of the box. Configure custom instrumentation and metrics with minimal setup for clearer production performance insights.
intouch/laravel-newrelic brings New Relic APM monitoring to Laravel applications with minimal setup. It hooks into the request lifecycle to assign meaningful transaction names and enrich New Relic data with application context, making performance traces and errors easier to diagnose.
- Transaction naming from routes, controllers, and actions
- Custom parameters for request, user, or app metadata
- Exception reporting and transaction ignoring for noise reduction
- Publishable config and configurable middleware
- Laravel package auto-discovery support
Frequently asked questions about Laravel Newrelic
- What is intouch/laravel-newrelic used for?
- It is a Laravel service provider package that wires the New Relic PHP agent into a Laravel application. It adds configurable transaction naming, custom instrumentation hooks, exception reporting, and Artisan commands to reduce boilerplate. It does not replace New Relic itself.
- Does intouch/laravel-newrelic support Laravel 8 or Laravel 9?
- No, the package is scoped to the Laravel 5 era and has had no release since February 2019. Laravel 8, 9, 10, and later are not supported by the published constraints without a fork. Run a compatibility spike or choose direct agent integration instead.
- How do I install intouch/laravel-newrelic in a Laravel app?
- Install it with Composer, publish its configuration, register the service provider or middleware as required, and enable it per environment. Confirm the illuminate and PHP constraints first because the package targets Laravel 5. Keep the New Relic PHP agent installed and verify behavior with config caching enabled.
- Do I still need the New Relic PHP agent installed with this package?
- Yes. The package is a thin integration layer and depends on the New Relic PHP agent being present on the host or container. Without the native extension, instrumentation can silently become a no-op. Confirm agent version and deployment model before adopting it.
- How does transaction naming work with intouch/laravel-newrelic?
- Transaction naming is one of the package's main features and is configured through its Laravel-side setup. Middleware order and route resolution matter, so validate names in a non-production environment. Incorrect ordering can produce misleading transaction names in New Relic.
- Can intouch/laravel-newrelic report exceptions and custom parameters to New Relic?
- The package provides exception reporting and custom instrumentation hooks for New Relic. Validate that your agent version supports the calls you rely on and that errors are captured as expected. Test both HTTP and non-HTTP paths if they matter to you.
- Is intouch/laravel-newrelic maintained and safe for production?
- Treat it as high lifecycle risk: it is effectively unmaintained, has no release since 2019, and has zero Packagist dependents. Pin an exact version or vendor an internal fork, add CI checks, and canary-test before production. Do not make it a strategic observability dependency without an exit plan.
- How do I test whether intouch/laravel-newrelic instrumentation works with and without the agent?
- Run a short spike with the agent installed and absent, then compare transaction names, exceptions, custom parameters, queue workers, and CLI jobs against a baseline. Check for silent no-op instrumentation and config-cache effects. This is mandatory before committing to the package.
- What are alternatives to intouch/laravel-newrelic for Laravel monitoring?
- Alternatives include direct New Relic PHP agent integration, a maintained internal fork, or an OpenTelemetry-based observability path. The package only reduces Laravel boilerplate and does not replace New Relic. Choose based on your Laravel version, agent model, and long-term ownership.
- Does intouch/laravel-newrelic support queues, CLI jobs, and config caching?
- Queue, CLI, and config-cache behavior must be verified rather than assumed. The package targets Laravel 5 and may be affected by middleware order, agent API drift, and configuration caching. Confirm those signals explicitly if you need queue or Artisan job visibility.
Weaver
How can I help you explore Laravel packages today?