Environments Revisited
Product
We have revisited the “Environments” feature of the Profiler and are stopping to collect performance data on non-production environments. With this change the user-experience becomes much better, because we can now always display the production data graphs. The environment switch dropdown was removed from the UI.
Our customers so far haven’t used performance data from other environments and we came to the conclusion that the additional complexity in the user-interface is only causing confusion.
Nothing has changed for regular profiling traces: They are still collected for every server and environment.
If you do need performance data, for example during load-tests of staging environment, you can just add a second application to your account and use that for testing.
About the author
I am the founder and CEO of Tideways. I started the company over 10 years ago with the mission to move the PHP ecosystem forward, starting with performance. As managing director, I work across product, strategy, and the day-to-day of building a developer-focused SaaS business.
I’m a core contributor to the Doctrine open-source project and a founding board member of the PHP Foundation, which reflects my long-standing commitment to the PHP ecosystem. I particularly enjoy working at the intersection of application performance, developer experience, and the open-source community that makes PHP what it is. Outside of work, I enjoy board games, hiking, and coffee.