Flare Flare Laravel Laravel PHP PHP JavaScript JavaScript Protocol Protocol

Attributes

The attributes object is a flat key-value map that contains all context data for the error. Resource and scope attributes are merged into this single object.

Include as much context as possible: service info, host and OS details, git state, runtime info, request data, routing details, user info, etc. The more attributes you provide, the more useful Flare's filtering, grouping, and debugging tools become.

For the full list of recognized attribute keys, see Resources.

Some event types are inlined as attributes on the error rather than added to the events array. For example, php_request and php_routing attributes are placed directly in the root attributes object. See the individual event type documentation for details.

Entry Point

Flare uses the following attributes to determine the entry point of the error:

Attribute Description
flare.entry_point.type Entry point type: web, cli, or queue. Defaults to web if not provided
flare.entry_point.value The URL or command that was being executed
flare.entry_point.class The handler class (e.g. controller, job class)

Exception Context

The context.exception attribute can contain additional context provided by the exception itself. This is an object with arbitrary key-value pairs that the exception class defines, useful for attaching structured debugging data to specific error types.

Livewire

When the error occurs during a Livewire request, include the livewire.components attribute with the component data for the request. Each entry represents a Livewire component involved in the request.

Attribute Type Description
livewire.components array Array of component objects

Each component object:

Field Type Description
component_class string/null Fully qualified component class name
component_id string Unique component instance ID
component_alias string/null Component alias
data object Component public properties/state
memo object/null Component metadata (id, name, path, method, children, errors, locale)
updates array Data updates sent in the request, each with type and payload
calls array/null Method calls on the component, each with path, method, and params

Database Errors

When the error is a database exception (e.g. QueryException, PDOException), it is recommended to include the db.statement attribute with the SQL query that caused the error. Flare uses this to improve error grouping for SQL errors.

Jobs & Commands

When an error occurs during a job or command, include a laravel_job or php_command event in the events array with the appropriate failure attribute (laravel.job.success set to false for jobs, or process.exit_code for commands). This allows Flare to track failure rates alongside the error.

Payload Sourcemaps