Blackfire Monitoring is currently in the Early Bird phase. A subscription to Blackfire Premium or Blackfire Enterprise is required to activate Monitoring.
Read more on our pricing page.
Blackfire Monitoring currently supports PHP 7 and higher on Linux, BSD, macOS and Windows (via Windows Subsystem for Linux). Python support is in Beta.
Once you have subscribed to Blackfire Monitoring, you should activate it on the relevant environment:
This requires to have admin rights on the environments, or to be the subscription owner.
You can disable Monitoring on an environment any time your need.
Additional settings are available, at the environment level.
The Sample Rate represents the percentage of your PHP requests which you would like Blackfire to monitor.
Each request which is monitored generates a “Trace”.
As Blackfire Monitoring pricing is based on a quota of Traces, you can balance:
Note that this tracing level captures basic performance metrics, such as overall response time and memory usage, and generates close-to-no overhead.
The Extended Sample Rate represents the percentage of Traces for which Blackfire will collect more in-depth metrics.
Especially, such Extended Traces will include Spans.
A Span is the representation of a function call over time, just like in a profile timeline.
Collecting Spans may generate additional overhead on Extended Traces.
With the Extended Sample Rate, you can balance:
The Span Time Threshold represents the minimum amount of time spent in a function call so that a Span will be collected for that call.
Spans are displayed on a Transaction view.
With the Span Time Threshold, you can balance:
Blackfire Monitoring natively supports all PHP applications. For some frameworks, including Symfony, Drupal, Prestashop 1.7+, and Ibexa DXP, Blackfire Monitoring already collects the most significant Spans, while avoiding to add more than 15% overhead (maximum currently measured).