Weave Code
Palzin Php Laravel Package
palzin-apm/palzin-php
Palzin APM for PHP and Laravel gives you real-time application monitoring: track slow requests, database queries, errors, and exceptions, then send it all to the Palzin dashboard for fast debugging and performance insight.
Monitoring Package
Frequently asked questions about Palzin Php
- How do I install Palzin APM in a Laravel application?
- Install the client with Composer using palzin-apm/palzin-php, then publish any provided configuration so you can supply your Palzin APM ingestion key. Laravel auto-discovery registers the service provider so request, query, and exception tracking starts without extra wiring. After that, run a few requests and confirm data appears in your Palzin dashboard.
- Does palzin-apm/palzin-php support Laravel 10 and Laravel 11?
- The package ships a first-class Laravel integration built on the framework's service provider and middleware conventions, so it targets current Laravel releases. Check the composer.json constraints on Packagist for the exact supported PHP and Laravel version ranges before upgrading. If you are on an older Laravel version, verify compatibility first or pin the package version that matches your framework.
- How much performance overhead does Palzin PHP add in production?
- Palzin PHP is designed as a low-overhead instrumentation layer, and the README highlights configurable sampling as the main lever for controlling cost. Sampling lets you record only a percentage of requests and jobs, which keeps memory and network usage predictable on high-traffic applications. Always benchmark on a staging copy of your app with production-like traffic before enabling full sampling in production.
- How do I configure sampling to reduce the volume of data sent to Palzin?
- Sampling is configured through the package configuration, where you set the fraction of requests and background jobs that should be recorded and shipped. Lowering the rate reduces ingestion volume and outbound network calls, which matters most on high-throughput endpoints. Keep a higher rate on critical or slow routes and a lower rate on noisy health checks and asset endpoints.
- Can Palzin monitor background jobs and queue workers?
- Yes. Palzin PHP includes job and queue monitoring so work handled by queue workers is reported to the Palzin dashboard alongside web requests. That lets you spot slow or failing jobs and correlate them with the requests that dispatched them. Make sure the instrumentation is loaded in your worker processes, not only in your HTTP stack.
- How does Palzin track database queries and slow endpoints?
- The client hooks into your application to automatically capture requests and the database queries executed during them, then builds timeline traces of what happened. Those traces are sent to the Palzin dashboard, where you can inspect the slowest segments and identify which queries or calls dominate a request. This makes it practical to diagnose slow endpoints in production without adding ad-hoc logging.
- How do I disable Palzin APM in local development or during tests?
- Keep the ingestion key out of your local .env file or set an explicit enabled flag to false in the package configuration for non-production environments. Most teams only enable the client on staging and production so test suites stay fast and do not generate network traffic. Confirm the service provider exits early when disabled so no background shipping occurs.
- Does Palzin PHP work outside Laravel, in plain PHP projects?
- Yes. The core is framework-agnostic, and Laravel support is layered on top as a first-class integration. In a plain PHP application you initialize the client and instrument the segments you care about yourself. That makes it usable in legacy codebases or custom frameworks where a Laravel service provider is not available.
- How do I capture exceptions and errors and send them to Palzin?
- Palzin PHP hooks into exception handling so unhandled errors are recorded automatically and attached to the request or job trace they occurred in. That context, including the surrounding timeline, is what makes production debugging faster than reading a raw stack trace. For caught exceptions you want to report manually, use the client API to record them explicitly.
- Is Palzin APM a good alternative to Laravel Telescope or Sentry?
- They solve different problems. Telescope is a local debugging tool that stores data in your own database, while Palzin APM is a hosted dashboard focused on production performance monitoring across requests, queries, jobs, and exceptions. If you need consolidated production tracing with sampling and timeline views, Palzin fits that role; if you want an in-app inspector for local development, Telescope still works well alongside it.
Weaver
How can I help you explore Laravel packages today?