Laravel Logzio Laravel Package

Getting Started

Start by checking the package’s composer.json constraints against your Laravel version before adopting it; v1.1.1 is a 2021 release, so do not assume compatibility with newer Laravel versions without testing. Install with Composer, publish the package config, and wire its logging channel into config/logging.php.

Set the minimum environment values:

LOGZIO_TOKEN=your-logzio-token
LOGZIO_REGION=uk

The v1.1.1 release adds UK as a supported region. Use uk when UK data residency is required; otherwise use the region matching your Logz.io account. The first practical use case is a dedicated production log channel that ships Laravel application logs to Logz.io while keeping a local fallback channel.

Look first at:

1. The package README and published config for the exact channel driver/options.
2. config/logging.php for channel wiring.
3. Your Logz.io account settings for the correct token and listener region.

Validate with a single test log from a staging environment before routing production traffic.

Implementation Patterns

Use a dedicated Logz.io channel rather than replacing all local logging. A common pattern is a Laravel stack channel that keeps local daily logs and adds Logz.io for centralized search:

'channels' => [
    'stack' => [
        'driver' => 'stack',
        'channels' => ['daily', 'logzio'],
    ],
],

Configure the package-provided Logz.io channel with environment-specific token and region values. Keep region selection in .env per environment so staging and production cannot accidentally ship to the wrong Logz.io region.

Use Logz.io’s type/service metadata to separate applications, queues, and scheduled jobs. Add Monolog processors for stable fields such as app, env, release, request_id, and queue_job_id; this makes Logz.io queries and dashboards much more useful than raw messages.

For day-to-day Laravel work:

• Route critical application logs through Log::channel('logzio') or the stack.
• Keep local logs enabled for incident debugging when the network or Logz.io ingestion is unavailable.
• Test the channel explicitly with Log::channel('logzio')->info('test').
• Use structured context arrays instead of string interpolation.
• Avoid logging secrets, tokens, passwords, full request bodies, or personal data.

For high-volume services, review log volume and sampling before enabling the channel broadly. Logz.io ingestion has cost and network implications, and synchronous log shipping can add latency if the transport is slow or unavailable.

Gotchas and Tips

• UK region requires v1.1.1 or later. If you need UK data residency, upgrade and set the region explicitly. Older versions will not recognize the UK option.
• Clear config cache after changing region or token: php artisan config:clear or php artisan config:cache as appropriate.
• Region and token must match. A mismatched region can result in dropped or rejected logs that are difficult to diagnose from Laravel alone.
• Do not assume modern Laravel support. Check composer constraints and run a staging test before using this package on Laravel versions newer than the package’s release era.
• Logging should not take down the app. Test behavior when Logz.io is unreachable, DNS fails, or the token is invalid. Keep a local fallback channel and consider whether the handler can throw during request handling.
• Ingestion is not instant. If a test log does not appear immediately, check the Logz.io listener/region, token, and network egress before changing application code.
• Use processors as the main extension point. Custom Monolog processors are usually cleaner than wrapping every Log:: call.
• The GitHub Workflow change in v1.1.1 has no runtime impact. The meaningful upgrade reason is UK region support.

Overall, v1.1.1 is a small but useful release for teams needing UK Logz.io shipping. The package is practical for Laravel apps already standardized on Logz.io, but it should be adopted with version-compatibility checks, a local fallback channel, and clear rules around sensitive data.