Monitoring and Profiling yields much better data if you can assign a transaction name to every request that is triggered in your project. If you don’t do this, then every transaction will automatically get the name 'default' in version 4, and the last two parts of SCRIPT_FILENAME (for example web/index.php) in version 5.

If you are using an MVC framework with controllers and actions, then a separation into the controller class and action method names for the transaction names yields much better results. Look at PHP-Extensions-API-Calls to detect Transaction Names in your application code.

Compare these two results that you get on your project dashboard, the first one using only default transaction:

Without Transaction Names

and the second one collecting data with transaction names:

With Transaction Names

Adding transaction names allows you to see bottlenecks, number of requests and response times for each of these transaction individually, including historical data and graphs. Additionally it will group the profiling traces based on these transactions.

Configuring Human Readable Names

After you have started using transaction names based on framework or manual support, you can go one step further and configure human readable name for all transactions or just for the ones which you care about the most. Doing so improves the utility of Tideways, because it frees you from having to know what page each listed controller/action is responsible for — especially for the non-technical users in the weekly report. For example in the transaction list:


Or in the transaction detail page:


To configure a human-readable transaction name:

  1. Go to Project Settings  Transactions

  2. Click the configure transaction (pencil) icon, at the far right-hand side of the transaction which you want to name

    View the list of transactions under the project’s settings
    Figure 1. View the list of transactions under the project’s settings
  3. Specify a name for the transaction in the Name field, and then click Save

    Setting a transaction’s name
    Figure 2. Setting a transaction’s name

Following this, you will then see the configured human-readable name, in the Name column, next to the transaction in the transactions list.

A transaction with a human-readable name
Figure 3. A transaction with a human-readable name

Transaction Limits

Transaction limits are available on the Tideways pricing page.

Still need help? Email [email protected]