Weave Code
Laravel Client Laravel Package
loglia/laravel-client
Laravel client for Loglia that streams application logs, exceptions, and contextual metadata to your Loglia dashboard. Lightweight integration with sensible defaults, configurable handlers, and easy setup for production monitoring and debugging.
A Laravel client for Loglia that streams application logs to a centralized dashboard. It integrates with Laravel’s logging stack via a configurable Monolog handler, so you can keep local logging while sending production logs to Loglia.
- Simple Composer installation with Laravel auto-discovery
- Environment-based configuration through
.env - Sends Laravel logs and exception context to Loglia
- Works alongside existing log channels
- Lightweight integration with no application code changes
Frequently asked questions about Laravel Client
- How do I install loglia/laravel-client in a Laravel application?
- Install it with composer require loglia/laravel-client, then publish the package config if it ships one and add your Loglia credentials. There are no migrations, queues, or extra infrastructure to provision. Once configured, Laravel's logging pipeline sends entries to your Loglia dashboard.
- Which Laravel versions does loglia/laravel-client support?
- The v3.1.0 changelog lists support for Laravel 8, which under semver is a minor, additive release. It does not explicitly confirm support for Laravel 10, 11, or 12, so read the illuminate constraints in the package's composer.json before assuming compatibility. If your app runs a newer major, check for a more current release line first.
- How do I configure Loglia credentials in Laravel?
- Credentials are normally supplied through environment variables alongside a published config file, so keep the API key out of source control. Rebuild your config cache after changing values so the running app picks them up. Confirm the exact config key names in the package's README or config file rather than guessing.
- Does loglia/laravel-client work with Laravel 10 or Laravel 11?
- That is not confirmed by the v3.1.0 changelog, which headlines Laravel 8 support. Composer will resolve against whatever illuminate range the package declares, so run a dry-run update to see which version your app would actually receive. If you are on Laravel 10 or newer, treat the L8 focus as a prompt to look for a current release line.
- What PHP version does loglia/laravel-client require?
- Laravel 8 permits PHP 7.3 through 8.1, so a constraint aligned with L8 may not install on PHP 8.2 or newer. Read the PHP requirement in composer.json and compare it against your production runtime image rather than your local dev PHP. A dry-run install fails early if the floor or ceiling conflicts.
- Is upgrading from 3.0.x to 3.1.0 safe?
- It should be a no-op at the application layer: a composer update with no code edits, no config republish, and no data migration. If your code does require changes, semver has been broken and that is the finding worth investigating. Avoid republishing vendor config on a minor bump, since it can overwrite local customizations.
- Is loglia/laravel-client safe to use in production?
- The integration itself is lightweight, just a Composer dependency that ships logs to the Loglia service. The main risk is maintenance cadence: a release whose newest headline feature is Laravel 8 support may trail your framework by several majors. Check the CI test matrix, any published support policy, and maintainer activity before depending on it in production.
- Does loglia/laravel-client require database migrations or extra infrastructure?
- No. It is a pure Composer package that forwards application logs and events to Loglia. You install it, configure credentials, and it hooks into Laravel's logging setup. Nothing needs provisioning beyond your Loglia account and API key.
- How can I test that logs are actually reaching Loglia?
- Write a test log entry in a staging environment and confirm it appears in your Loglia dashboard within a few seconds. Verify the config cache has been rebuilt and that the API key and endpoint values are correct. Keep production credentials out of local test runs to avoid polluting your real log stream.
- What are the alternatives to loglia/laravel-client for Laravel log management?
- Laravel's Monolog channels let you ship logs to services such as Sentry, Datadog, Papertrail, or Better Stack without a dedicated client package. Compare on retention, alerting, pricing, and whether each option supports your Laravel major. Loglia's focus is centralized dashboards for logs and events, so weigh that against more established alternatives.
Weaver
How can I help you explore Laravel packages today?