Inconsistent Profiling Durations in Sentry When Using Swoole

[mertasan]

How do you use Sentry?

Sentry SaaS (sentry.io)

SDK version

4.10

Laravel version

12.12.0

Steps to reproduce

We’re using PHP 8.4 with Laravel Octane, running on Swoole 6.0.2, and have enabled profiling in Sentry at a 1% sampling rate.

However, the profiling data in Sentry seems off — we see requests showing as taking 25 seconds, but when we open the trace details, there’s nothing inside.

According to Google Load Balancer logs, our request durations are never that high — usually 50ms max.

The endpoints we’re calling (external APIs) take around 3–4 seconds at most.

Since the trace details are empty, we’re unable to make sense of the numbers.

Could there be something wrong with how Sentry is recording or interpreting this data?

For example, one of the entries in the list — AppHomeController — only returns a simple HTML response, yet it’s shown as having the longest duration.

Any help would be appreciated.

Thanks!

Expected result

Actual result

[faytekin]

Same issue

[cleptric]

Is this just a regular Octane setup with Swoole? Or are you using something custom?

To make this extra clear for me, when you say profiling, you actually mean tracing?
So you set a traces_sample_rate/SENTRY_TRACES_SAMPLE_RATE of 0.01?
We also have a dedicated profiling product, which's rate is configured by profiles_sample_rate/SENTRY_PROFILES_SAMPLE_RATE.