Events
The Event instrumentation records Laravel events fired during a request or job as events on the current active span. This surfaces application-level event activity without adding extra spans to the trace. A single span event namedevent fired is added for each dispatched event, with the event attribute set to the fully-qualified event class name or string identifier.
Excluded Events
Many internal Laravel framework events are excluded by default to avoid noise:Illuminate\*Laravel\Octane\*Laravel\Scout\*Laravel\Horizon\*eloquent*bootstrapped*/bootstrapping*creating*/composing*
excluded configuration option:
Configuration Options
| Option | Type | Description |
|---|---|---|
excluded | string[] | Additional event class names or string identifiers to exclude from recording. |
Disabling Events
EventInstrumentation::class from the instrumentation array in config/opentelemetry.php.
Views
The View instrumentation traces Blade view rendering by wrapping the view engine resolver. Each rendered view produces a dedicated span, allowing you to identify slow or deeply nested view hierarchies.- Span name: The view name (e.g.
users.index,components.button). - Span kind:
INTERNAL
Configuration
Inconfig/opentelemetry.php:
Disabling Views
ViewInstrumentation::class from the instrumentation array in config/opentelemetry.php.
Livewire
The Livewire instrumentation traces Livewire component lifecycle events (mount and hydrate/dehydrate cycles). Each component render produces a span namedlivewire component with component.name and component.id attributes.
This instrumentation is a no-op if the
livewire/livewire package is not installed.Configuration
Inconfig/opentelemetry.php:
Disabling Livewire
LivewireInstrumentation::class from the instrumentation array in config/opentelemetry.php.