How does the Symfony profiler get its information?
The profiler gets its information using some services called “data collectors”. Symfony comes with several collectors that get information about the request, the logger, the routing, the cache, etc. Run this command to get the list of collectors actually enabled in your app:
What is webprofilerbundle in Symfony 5.3?
Symfony 5.3 is backed by JoliCode. The WebProfilerBundle is a development tool that provides detailed technical information about each request execution and displays it in both the web debug toolbar and the profiler. All these options are configured under the web_profiler key in your application configuration.
Do you need a custom Symfony data collector?
If you want to measure the time some tasks take in your application, there’s no need to create a custom data collector. Instead, use the built-in utilities to profile Symfony applications. Consider using a professional profiler such as Blackfire to measure and analyze the execution of your application in detail.
How does the debugbundle work with Symfony?
The DebugBundle integrates the dump () function even more into Symfony. Now if you use dump (), instead of printing in the middle of the page, it puts it down here on the web debug toolbar. You can click it to see a bigger version.
When to use Symfony in a functional test?
Symfony 5.3 is backed by JoliCode. It’s highly recommended that a functional test only tests the Response. But if you write functional tests that monitor your production servers, you might want to write tests on the profiling data as it gives you a great way to check various things and enforce some metrics.
What should be the header value for Symfony debug toolbar replace?
However, you can set the Symfony-Debug-Toolbar-Replace header to a value of 1 in the response to the AJAX request to force the refresh of the toolbar: Ideally this header should only be set during development and not for production. To do that, create an event subscriber and listen to the kernel.response event: