-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any plans to add support for ZTS again now when Frankenphp is gaining popularity in Laravel community #864
Comments
This also applies to Symfony users as their default docker setup also changed to Frankenphp. Frankenphp is currently incompatible with ZTS and thus by NewRelic. I do see an issue being closed where one asked for ZTS: #233. The questions asked in that issue were not answered. Instead, it was refered to https://docs.newrelic.com/docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-5-0-317/ I cannot find resources explaining why ZTS was removed. The maintainer of Frankenphp did explain why ZTS is a requirement for FrankenPHP What do we need to get a ZTS build? Or is there a technical reason why it cannot be created anymore? In that case one have to choose for FrankenPHP XOR NewRelic. |
I'm also curious why New Relic dropped support for ZTS, nowhere in your docs do you explain why it was dropped. My company is looking to move to frankenphp to benefit from the performance boost it'll give us. |
Second that, we'd be also interested in using Frankenphp but New Relic is blocking us. |
+1 |
We are using FrankenPHP and New Relic but because we couldn't use the official plugin we are using Open Telemetry instead. Not as feature complete but it's better than nothing. Hopefully, New Relic re-add a ZTS version of the plugin soon |
+1 for being able to use it in FrankenPHP images |
the link seems to be restricted to those inside their jira organization so going to assume that's a ticket for adding multi-threading support back to the PHP new relic agent. |
I just migrated to Frankenphp as many in the Laravel community is doing now and it will only grow as it now has first party support by Laravel, even though it's still in beta. But it's the most performant combo.
And it uses a ZTS compiled version of php and according to the creator is has use that.
So therefor I'm asking if you can reconsider the dropping of ZTS support and making it supported again? As it will be a bottleneck for a lot of Laravel users moving forward so they cannot continue to use New Relic as a service, and we are one of them.
The text was updated successfully, but these errors were encountered: