Skip to content

v0.2.1 — built-in Cloudflare geo + browser-ingest enrichment

Choose a tag to compare

@sylvesterdamgaard sylvesterdamgaard released this 06 Jul 22:48

Added

  • Built-in Cloudflare geo, and server-side geo/UA enrichment at browser ingest. With TELEMETRY_ANALYTICS_GEO=true, client.geo.country resolves from Cloudflare's CF-IPCountry edge header — free on every plan, no MaxMind database, no per-request lookup. Precedence: resolveClientGeoUsing() hook → CF-IPCountry → MaxMind. CF-* headers are only trusted when the request arrives through a trusted proxy — set Laravel TrustProxies to the immediate hop (your Cloudflare ranges, or your load balancer in a CF → LB → app chain); spoofable and ignored otherwise, and the XX/T1 sentinels are dropped. Toggle with TELEMETRY_ANALYTICS_GEO_CF (default on). The browser ingest endpoint now stamps geo and parsed user_agent.* on browser spans and events from the server-side ingest request, so nearly all analytics enrichment happens in one place.

  • Livewire update requests are named after their component. The Livewire update catch-all endpoint is now named livewire:{component} (batched: livewire:batch) on the span, span name and request metric, with the full list in livewire.components. An app's own resolveRouteUsing() still wins.

Changed

  • Removed internal architecture-decision records and the prior-art research survey from the published docs.

Full changelog: v0.2.0...v0.2.1