Tideways 2025.3 Release

In our third Release of 2025, you’ll uncover new ways to correlate data, debug critical bottlenecks, and streamline your workflow.

Over the last few months, we have been working on powerful new features and refinements for you; designed to give you more in-depth visibility, more automation, and smoother workflows.

We’ve added Performance Correlation in our service overview, so you can now spot dependencies and degradations system-wide at a glance.

To make troubleshooting smoother, Tracepoints can now be triggered automatically, along with further improvements that give you faster, more precise profiling results.

For Shopware users, we’re introducing powerful new debugging options for the HTTP Cache, while an improved Transaction Tagging API gives you cleaner, more flexible insights across all environments.

We expanded crawler monitoring for assessment of their impact on app performance.

We’ve also sharpened instrumentation:

– Magento 2 template insights for spotting hidden inefficiencies.

– HTTP Location header instrumentation for more complete visibility.

– Enhanced TYPO3 and AMQP insights, closing gaps in instrumentation.

On top of that, quality-of-life features like choosing the default organization shown right after login make everyday use simpler and more intuitive.

More correlation. Smarter insights. Smoother workflows. With this Release, you’ll be ready to track performance from every angle and resolve issues faster than ever.

Enjoy and see how Release 2025.3 helps you push your application performance to the next level.

Summary

• Correlation In Service Overview
• Trigger Tracepoints Automatically
• Other Tracepoint Improvements
• Debugging Capabilities for Shopware Cache
• Improved Transaction Tagging API
• Monitoring Crawler Impact
• Improved Magento 2 Template Insights
• HTTP Location Header Instrumentation
• Improved TYPO3 Insights
• Improved AMQP Insights
• Select Organization shown after Log-In

Correlation In Service Overview

Through the “Service Overview” feature, Tideways allows you to pinpoint performance issues in different parts of your application. But as these services are often still connected, comparing their performance directly can reveal hidden dependencies and system-wide slowdowns.

With the new ‘All’ option in the performance screen, you can now view and compare performance graphs across all services in your project at once.

Hovering over a timeslot will make the familiar detailed tooltip for that service appear, while the same timeslot is highlighted across all other charts, making cross-service correlations effortless.

• Documentation: Service Overview

Trigger Tracepoints Automatically

Tideways now allows to configure the automatic creation of tracepoints on a schedule for the transactions of a service that have the highest performance impact.

In the Project Settings, you find a new section “Tracepoints” that allows you to configure these automatic tracepoints.

This feature is currently limited to the current request-based plans only and for all these projects, an automatic tracepoint was created already that creates a tracepoint, including callgraph collection, for the highest impact transaction once a day.

Based on this regularly available call graph trace, Tideways can detect more bottlenecks automatically and provide you with fresh insights every day in the “Observations” tab.

Additionally, Tideways can store these traces via Callgraphs in the trace history with long-term retention, enabling you to compare call graph data months or even years apart—and clearly see where your code has regressed over time.

• Documentation: Tracepoint Configuration

Other Tracepoint Improvements

Callgraph Tracepoints Activated By Default

When creating a new Tracepoint, the “Activate Callgraph Profiler” checkbox is now toggled on by default, because we saw the majority of tracepoints were created with Callgraphs activated.

Start Again Button for Tracepoints

A completed tracepoint can now be restarted with the same settings and duration again, by clicking on the „Start again“ button.

Debugging Capabilities for Shopware Cache

For Shopware, Tideways will now also collect the context information influencing the page cache key, making it easier to determine why a specific transaction could not be served from the page cache.

Improved Transaction Tagging API

The \Tideways\Profiler API now includes new methods getTags(), addTag(), and removeTag(). These allow you to build up the list of tags incrementally at different stages of a transaction. For example, adding an “authenticated” tag during bootstrapping and a controller-specific tag later when the controller runs.

The page cache instrumentation, which automatically sets cached and uncached tags, received an in-depth rework. Instead of a Shopware-specific solution, it now includes direct support for Symfony’s HTTP cache, benefiting all Symfony applications and implicitly fixing some bugs within Shopware’s page cache support—for example around stale responses.

The cached and uncached tags added by the automated instrumentation and the Profiler::markPageCache*() methods will also no longer overwrite any other tags already set for the transaction.

• Documentation: Custom Tags
• Documentation: Page Cache Hit Rate API

Monitoring Crawler Impact

Crawlers, bots, and robots have always been an influential source of traffic on public-facing web applications, and with AI bots doing more and more work on behalf of users, this share is increasing recently.

To allow debugging performance issues caused by crawlers, Crawler Detection for traces was added in the 2024.3 Release of Tideways.

In this Release we are expanding its use into Monitoring: You can now see the percentage of crawlers in the current monitoring timeframe as a percentage and in the tooltip for each time slot. You can also see the crawler ratio in the history data at the daily, weekly, and monthly granularity.

Improved Magento 2 Template Insights

Information captured for Magento blocks has been extended. Block events now contain both the name and class name of a block instead of just a block, and new events for rendered template blocks have been added.

HTTP Location Header Improvements

Tideways will now store the redirect target (location response header) as an annotation on the root span.

This helps debugging and understanding in the cases where it’s important to know where exactly a request was redirected to.

Improved TYPO3 Insights

Tideways now includes automated instrumentation for TYPO3, including transaction naming, automated service detection, page cache tagging support, and Fluid Template spans.

• Documentation: Compatibility and Requirements
• Documentation: Supported Frameworks and Databases

Improved AMQP Insights

The existing AMQP instrumentation for both the amqp extension and the php-amqplib/php-amqplib composer library has greatly been extended.

• The timeline now includes spans for the connection establishment and opening a new channel.
• The publish command now includes annotations for the channel ID and improves reliability for the existing annotations for routing key and exchange name.
• For the amqplib composer library, time spent communicating with the AMQP service will now be tracked more accurately within the “Queue” layer.

Select Organization shown after Log-In

For users with access to multiple organizations, any one organization can now be marked as default by clicking on the star icon and will then be visible immediately after logging in.