We moved a legacy production environment to PHP 8.2 after rebuilding parts of the underlying system. The logs and metrics look okay so far. How much confidence should we have in that, and what should we check next?
We upgraded production to PHP 8.2. What should we watch for now?
Answers
Clean logs on day one are encouraging, not a full test. The awkward failures may be in a Sunday cron job, a background worker, an old integration or a code path that only gets used once a quarter.
Make an inventory of scheduled jobs and workers, check that they actually run to completion, and watch their logs as well as the web server. For anything that runs rarely, see whether you can safely exercise it rather than waiting months to find out.
Reply to this answer
I'd treat 8.2 as a stepping stone. Its security support ends at the end of 2026, so there's not much runway left. Plan the next PHP upgrade now rather than waiting for another emergency.
That doesn't mean you had to jump straight to the newest release. Dependencies can have breaking changes, and an old operating system or toolchain may constrain which PHP versions you can build. Check the requirements for your target version and test the application and its dependencies together.
Reply to this answer
The PHP version is only one piece of the risk. Check the support and patch status of the OS, libraries, extensions and application dependencies too. A newer runtime on top of unsupported components doesn't fix vulnerabilities in those components.
Keep a routine for reviewing security updates and applying patches. No upgrade guarantees there won't be a new vulnerability tomorrow, but maintained software gives you a path to fixes.
Reply to this answer
I'd put some time into recovery before calling it done. Check that backups are usable and that the team knows how to roll back the application and environment if a serious problem shows up. The rebuild may have changed assumptions in the old recovery process.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_m64!rivetcaper.8:
Also check worker processes have restarted onto the new runtime. A successful web request doesn't tell you what a long-running worker is using.