FPM worker output not going to logs
See original GitHub issueWith reference to #103, we’ve recently encountered the same issue and are considering using a forked buildpack to accomplish app log capture across our PHP CF deployments, which isn’t ideal from a maintenance point of view.
Given that logging to stdout is fairly idiomatic when dealing with cloud environments (e.g. https://12factor.net/logs), is there any appetite to default the catch_workers_output
php-fpm.conf setting to yes?
Alternatively, could some configuration be introduced to specifically target this setting which would mitigate the need to fully replace the php-fpm.conf file?
Steps to reproduce are the same as per #103.
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running cf curl /v2/info && cf version
?
- Cloud Foundry version is v241
- CLI version 6.11.3
What version of the buildpack you are using? 4.3.15
If you were attempting to accomplish a task, what was it you were attempting to do? View application logs as output by the app to stdout
What did you expect to happen? Application logs to appear in aggregated logging
What was the actual behavior? Application logs are not captured
Please confirm where necessary:
- I have included a log output
- My log includes an error message
- I have included steps for reproduction
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:18 (5 by maintainers)
Top GitHub Comments
Hi @beequeue,
We’re going to implement this more generally than the solution on @dmikusa-pivotal’s branch. Follow https://www.pivotaltracker.com/story/show/141979329 for details.
Thank you to all those who worked on this, it’s a great help to us 👍