Controlling Blackfire Monitoring with Transactions API

By Thomas di Luccio, on Aug 25, 2021

Monitoring is the cornerstone of Blackfire’s Continuous Observability solution. By getting instant insights into their application’s behavior, our customers gain a head-start on improving their performance by knowing exactly where to look for the most impactful optimization.

By default, Blackfire Monitoring collects information on all incoming transactions, and detects controllers from supported frameworks. Yet, in some cases, you may need some customization. The Transactions API is here to help.

Available for both PHP and Python, this API will let you:

  • name transactions: in most cases, transactions are automatically named after the class and the method names. In some specific cases, the name cannot be detected and those transactions are stacked under an unnamed transactions label. You could then manually name those transactions;
  • ignore transactions: in some cases, you may want to specify transactions that you don’t want or need to monitor, for instance to avoid any noise they could generate in the Monitoring dashboard is they are not relevant to your performance management strategy;
  • manage transactions (beta at the time of writing): CLI commands and consumers monitoring will require manual instrumentations defining where it should start and end.

Check the documentation to learn more about the API and how to get even more control over your monitoring.

Thomas di Luccio

Thomas is a Developer Advocate at Blackfire.io. He likes nothing more than understanding the users needs and help them find practical and empowering solutions. He’ll support you as a day-to-day user.