Profile Symfony requests and console commands with framework-aware performance monitoring
Perfbase helps Symfony teams isolate slow routes, service-container hotspots, console regressions, and database bottlenecks without turning observability into a custom project.
Why teams choose Perfbase for Symfony
Bundle configuration for Symfony apps
Covers HTTP and console contexts
HTTP status-code allowlist built in
Symfony
Automatic performance monitoring for Symfony applications
Supported versions
Symfony 5.4-7.x / PHP 7.4-8.5
Quick install
composer require perfbase/symfonyStarter config
# config/packages/perfbase.yaml
perfbase:
enabled: true
api_key: '%env(PERFBASE_API_KEY)%'
sample_rate: 0.1Use cases
Why teams use Perfbase for Symfony
Perfbase is built for teams that need more than a local debug toolbar. It brings production-facing traces, framework-specific context, and shared visibility across the slow paths that matter most in Symfony.
See route-level performance clearly
Understand which controllers, event subscribers, services, and queries are driving slow Symfony requests.
Keep console performance visible
Profile console commands instead of limiting visibility to web traffic.
Move faster without custom plumbing
Use a framework-native integration instead of wiring your own tracing layer around Symfony internals.
Profiling coverage
What gets profiled and how Perfbase works in Symfony
Perfbase stays framework-aware while keeping setup light. These are the behaviors and operational paths this integration is built to expose.
HTTP profiling
Automatic profiling via kernel event subscriber, with the trace submitted after the response is sent.
Console command profiling
Console commands are profiled through Symfony console event listeners.
Bundle registration
Register the bundle manually unless your app already consumes a published Symfony Flex recipe.
Include and exclude filters
Filter by route pattern, route name, controller, or command name.
Client provider
Inject the Perfbase client provider for manual profiling where automatic subscribers are not enough.
Fail-open design
Profiling errors never crash your application, and debug mode is available for development.
Setup preview
How to get started with Perfbase in Symfony
Start with install, configuration, and the first framework-specific profiling steps here. When you want full implementation detail, each card links directly into the complete guide.
Installation
Install the Perfbase PHP extension first. This is what does the actual profiling:
Open docs section →
Configuration
Create a starter config with your API key and enable profiling:
Open docs section →
HTTP profiling
HTTP requests are profiled automatically via a kernel event subscriber, with no middleware to register. The subscriber hooks into four kernel events:
Open docs section →
Console command profiling
Symfony console commands are profiled automatically via console event listeners. The subscriber handles ConsoleEvents::COMMAND, ConsoleEvents::ERROR, and ConsoleEvents::TERMINATE.
Open docs section →
FAQ
Symfony profiler and performance monitoring FAQ
Can Perfbase profile Symfony Messenger workers?
Not as a dedicated worker lifecycle today. Messenger work that runs inside a profiled HTTP request or console command is captured as part of that trace.
Does Perfbase replace the built-in Symfony profiler?
No. Symfony profiler is excellent for local debugging, while Perfbase is aimed at production-oriented profiling and performance monitoring across real traffic and background work.
Can I add manual spans in Symfony services?
Yes. The SDK is available through the container so you can add targeted manual spans or attributes where automatic instrumentation is not enough.
Start profiling
Ready to start profiling production traffic?
Create a project, install the package, and start capturing framework-level traces in minutes.