Shift performance management left

QRebel helps development teams find, diagnose, and fix application performance issues earlier in the continuous delivery pipeline. By checking each build for performance regressions during test runs, QRebel uncovers problems before they impact the user experience.


Performance complaints from users can have a direct impact on your revenue and often by the time you hear them, it’s too late to recover. According to the Developer Productivity Report 2015, 75% of performance issues are discovered in production. Use QRebel to shift performance testing left. It is a clear improvement.

QRebel Features

Find performance issues before they affect users

With QRebel, your team finds inefficient code, excessive IO, and exceptions in your development and test environments, catching regressions early to identify issues and improve application performance.

Use existing tests and environments to uncover performance issues

No need to write new tests. QRebel monitors applications running in existing test or development environments. Regressions can automatically fail builds in your continuous integration, preventing bad builds from reaching production.

Fix issues effortlessly with actionable profiling data

QRebel pinpoints the exact issue that caused a regression by continuously monitoring builds and versions. QRebel also identifies end-to-end stacktraces between multiple JVMs, raw database queries, and request parameters to help developers fix issues fast.

Shift performance management left

Find, diagnose, and fix

QRebel catches harmful performance regressions during the development and testing stages. By monitoring team code changes during test runs and reporting issues across builds, QRebel makes it simple to find, diagnose, and fix issues before they affect your end users.

  • Regression detection

    QRebel automatically compares performance results between builds to show how code changes from the team impact performance.

Track service-level agreement

Receive alerts about endpoints exceeding maximum request duration and IO count per transaction.


Make QRebel part of your continuous integration pipeline with flexible REST API to prevent troublesome builds from making their way to production. REST APIs are easy to integrate with different tools in your continuous delivery such as Github, Jenkins, TeamCity, Bamboo…

Daily email reports

Daily email reports will let you know if any slow requests, excessive IO or exceptions were found. The reports will give an overview of affected applications and end points.

  • Automatic trace differences

    QRebel allows you to compare full stacktraces against a baseline to find the root causes of slow requests, slow and excessive IO, and exceptions for any transaction. QRebel also identifies added or removed method calls compared to the baseline transaction.

Lossless Latency Profiling

Every single request from test runs is taken into account to provide an accurate picture of performance regressions and improvements occurring between releases.

Builds and versions

New builds and versions are automatically picked up represented on a timeline. This allows to exactly pin-point when a regression occurred.

End to end tracing

Track a transaction as it makes its way through multiple services to easily find the service that has regressed.


See both SQL and NoSQL raw queries, with full information on what was executed and how long it took.

Web service calls

Measure outbound HTTP requests to REST APIs and third-party services that the application uses, as well as tracking RMI and messaging queues such as JMS, ActiveMQ, SpringJMS, Spring AMQP, and RabbitMQ.

Track issues

Built-in JIRA integration allows you to create tickets within QRebel, ensuring found regressions are presented to development teams with the necessary information to fix any issues.

QRebel Documents

Contact Us