This way of defining scenarios is deprecated. You should migrate your
scenarios to the new format instead.
Blackfire Scenarios builds on Blackfire Tests.
Blackfire scenarios are a list of important URLs to profile on a regular
basis, like when you deploy your code on a staging environment or in
production, when you create a pull-request to add a new feature or fix a bug,
… The idea is to assess the performance of your code and to check its
Note that scenarios are only able to express HTTP requests, they cannot be
used for CLI commands.
Scenarios are run when triggered; the result
of triggering a scenario is a report accessible on blackfire.io that has a
status (pass or fail) that can be notified to users.
Other Ways to Automate Scenarios
You can write your own HTTP scenarios by using our PHP SDK or our integration with Goutte or Guzzle.
You can also write scenarios “manually” via PHPunit for libraries or CLI commands and automatically
benefit from the builds and notification channels of your continuous integration
Like Blackfire tests, scenarios are defined in the
- path: /docs/validator
Validate .blackfire.yaml files via the Blackfire online
Each section defines a scenario and accept the following settings:
Scenarios currently have the following limitations:
For more complex scenarios, use Goutte or
When a scenario is triggered, it generates a report and notifications are sent.
The build report is available from the dashboard under the Builds section.
Builds have a retention policy of 13 months and their profiles are subject
to the retention policy of your plan.