Logentries Bundle Laravel Package

Getting Started

Start by reviewing the package README and publishing its config if it provides a config file. The main change in v1.0.3 is that the UDP transport host is configurable, so look first at the UDP transport/connection settings in the package config.

Typical first use case: sending telemetry/logging/analytics events over UDP to a collector that is not on localhost, such as a Syslog, StatsD, or custom UDP listener.

Set the UDP host via config or environment:

// config/<package>.php
'udp' => [
    'host' => env('PACKAGE_UDP_HOST', '127.0.0.1'),
    'port' => env('PACKAGE_UDP_PORT', 514),
],

Then configure the package to use the UDP transport and send a simple test event from a Laravel command or tinker session. Verify receipt on the collector side before wiring it into application flows.

Implementation Patterns

Use environment-specific UDP hosts so local development, staging, and production can target different collectors:

PACKAGE_UDP_HOST=udp-collector.internal
PACKAGE_UDP_PORT=514

Common day-to-day patterns:

• Centralized telemetry: Point all app instances at a shared UDP collector host rather than relying on localhost forwarding.
• Per-environment routing: Use different hosts for local, staging, and production, but keep the same transport code.
• Per-channel overrides: If the package supports multiple transports/channels, configure the UDP host only for channels that use UDP and leave other transports untouched.
• Container/service networking: In Docker or Kubernetes, set the host to the collector service name or internal DNS name.
• Feature rollout: Introduce UDP telemetry in a single job or listener first, verify collector ingestion, then expand to broader application events.
• Testing: In Laravel tests, either disable the UDP transport, point it at a local test listener, or fake the package’s underlying sender if it exposes a fake/test hook.

Keep host/port configuration in config files and environment variables rather than hard-coding it in application code. This lets infrastructure changes happen without code deployments.

Gotchas and Tips

• Config caching: After changing the UDP host in .env or config, run php artisan config:clear locally and ensure production deploys rebuild config cache with php artisan config:cache.
• UDP is fire-and-forget: UDP does not guarantee delivery, ordering, or retransmission. Do not use it for critical business events unless you have collector-side monitoring and acceptance of loss.
• Host vs port: v1.0.3 makes the host configurable, but confirm the port setting is also correct for your collector. A valid host with the wrong port will silently fail.
• DNS and network policy: UDP hostnames must resolve from the Laravel host/container, and firewalls/security groups must allow outbound UDP to the collector port.
• IPv6: If using an IPv6 collector address, confirm the package’s UDP transport handles bracketed or raw IPv6 hosts correctly.
• Localhost defaults: If the default is still 127.0.0.1, production may appear configured but send only to the app container itself. Always set an explicit host outside local development.
• Debugging: Use tcpdump, collector logs, or a local UDP listener such as nc -ul <port> to confirm packets leave the app and arrive at the collector.
• Extension point: If the built-in UDP transport lacks needed behavior, look for a custom transport/sender extension point rather than modifying vendor code.