Getting Started

Install the package with Composer, publish its config, and point it at a dedicated log channel so slow-request entries are easy to grep and alert on.
Look first at the published config for three levers: the slow threshold, the request/component name filter, and the log destination. Tune the threshold per environment rather than using one global value.
First use case: enable it on staging, open a Filament page with a searchable/filterable table, and trigger a search. You should now see an origin such as livewire App\Filament\Pages\ListOrders[tableSearch], which tells you both the component and the wire:model property involved.

Implementation Patterns

Use a triage loop: capture slow request → read the origin → identify the Livewire component/property or route → optimize the query, eager loading, computed property, or debounce → re-test.
For Filament, write name filters against fully qualified class names. Since v0.3.1 accepts backslashes, you can target namespaces such as App\Filament\Pages\..., resources, and relation managers directly.
Treat the [property] suffix as the signal for wire:model interactions. Search, filters, and pagination often have no method call, so property-level origin is what lets you distinguish an expensive table search from a slow page load.
Keep thresholds environment-specific: lower locally/staging to discover issues, higher in production, or use an allowlist to focus on business-critical components and avoid noise.
Log to a dedicated channel and correlate entries with your existing observability (request IDs, user IDs, deployment markers). If the package exposes a formatter/resolver hook, enrich there rather than post-processing raw log lines.
Centralize filter patterns as Filament resources are added, especially for relation managers whose FQCNs are deeply nested.

Backslashes are now allowed in names, but if your name filter is regex-based you still need to escape them correctly in the pattern. Test the filter after upgrading and clear config cache (php artisan config:clear / config:cache).
Names are capped at 200 characters. Very long FQCNs, nested relation managers, or anonymous classes may still be rejected; prefer stable namespace prefixes in filters.
The origin lists updated property names only, not values, and no method name for wire:model updates. That is good for privacy, but you will not see the actual search term; use other logs if you need values, and be mindful of PII.
Remove any previous workaround that stripped backslashes or shortened Livewire class names. That workaround can now interfere with matching and hide the improved names.
Filament relation managers can produce deeply nested names; verify your filter covers the full namespace, not just page classes.
Slow-request logs can become noisy. Threshold and filters are the primary controls; if the package does not deduplicate or sample, aggregate externally.
v0.3.1 is a patch release with no signaled breaking changes. Upgrade, clear config cache, and verify with one real Filament search interaction to confirm class names and property origins appear as expected.