Livewire 3 requests are not identified as Livewire in transansaction

[hmazter]

How do you use Sentry?

Sentry SaaS (sentry.io)

SDK version

3.8.2

Steps to reproduce

1. Use Laravel with Livewire 3 (regular Livewire Components, not Volt)
2. Make livewire component update request, using the default POST /livewire/update endpoint
3. See the transaction in Sentry as /livewire/update

Expected result

I expect to see the component name in the transaction to differentiate between different component updates

Actual result

I see the default /livewire/update as transaction name

I guess this is being addressed in #736

[cleptric]

Thanks for writing in, we'll get the PR ready next week!

[stayallive]

Yes, correct, unfortunately Livewire team has made some drastic changes and no guide on how to migrate our current setup to their new structure. So we didn't complete the work yet to get our integration working for Livewire 3. If you have insights I'd be glad to accept some help on the PR otherwise we will eventually get to it!

[hmazter]

Thanks for the answer!
I'm pretty new to Livewire so I don't have any insight (yet) that could help 😄

[cleptric]

Did some research today

We can still listen to some events via LivewireManager::listen

• component.booted -> ???
• component.boot -> ???
• component.dehydrate -> dehydrate
• component.mount -> mount

There are zero docs, zero upgrade guides nor any meaningful PRs to look at, so this is very tedious.

To check for a livewire request, they now perform request()->hasHeader('X-Livewire').

[cleptric]

Support for Livewire 3 was added in v4.0.0.