Disclaimer : Attached file was shared by a user.
Using AppDynamics with LoadRunner
While it may seem at first look that AppDynamics is oriented towards IT Operations and DevOps, a number of our users have
been using AppDynamics for years within performance engineering practices. They realize many of the same benefits as their
peers in the IT Ops and DevOps practices. The key is to being proactive in avoiding performance issues prior to going live in
production. The following benefits are typically associated with integration of AppDynamics with load testing technologies:
–– Gaining deep application-level visibility to answer the ‘Why?’ vs. simply determining ‘What?’
–– Rapidly pinpointing bottlenecks in their environment
–– Comparing results across releases and performance tests
–– Improving performance by measuring the end-to-end performance from the end-user perspective
–– Increasing scalability of the application by optimizing software and avoiding unnecessary hardware investments
While some of this discussion centers on LoadRunner specifically, it is important to note that these use-cases may be applied
using any load testing solution and methodology, not just LoadRunner.
LoadRunner transaction integration
The simplest and fastest way to get LoadRunner transactions in AppDynamics is ‘painting’ your LoadRunner requests. This
method involves adding a custom header that contains the LR transaction name in the request so that AppDynamics can
display the transactions exactly as they appear in LoadRunner. Adding a custom header in LoadRunner is a simple process using
LoadRunner’s built in capability to set headers, including custom headers. The end-result gives you the same visibility as you
have in LoadRunner, but with the following added benefits:
–– Deep code-level visibility, in the context of a LoadRunner Transaction, end-to-end
–– Application container-level data such as Heap size and usage along with standard and custom JMX metrics
–– Deep database visibility, in the context of the transaction, including details SQL breakdowns
–– Extended visibility into application infrastructure (CPU, Disk, Network, and Memory).
AppDynamics provides these benefits automatically without the need to configure multiple HP tools, such as HP SiteScope, and
then configuring LoadRunner to pull these metrics from HP SiteScope.
It is a simple two-step process to gain this visibility:
1. A minor modification to your VUGen scripts to set the header, using the web_add_header() function.
2. A minor configuration tweak in AppDynamics to detect this new header and name transactions accordingly.
In addition, the AppDynamics integrations team is working on a utility that will help make these changes in the VUGen script
automatically (as of October 2015).
Download the file to keep reading.
Using AppDynamics with LoadRunner
While it may seem at first look that AppDynamics is oriented towards IT Operations and DevOps, a number of our users have
been using AppDynamics for years within performance engineering practices. They realize many of the same benefits as their
peers in the IT Ops and DevOps practices. The key is to being proactive in avoiding performance issues prior to going live in
production. The following benefits are typically associated with integration of AppDynamics with load testing technologies:
–– Gaining deep application-level visibility to answer the ‘Why?’ vs. simply determining ‘What?’
–– Rapidly pinpointing bottlenecks in their environment
–– Comparing results across releases and performance tests
–– Improving performance by measuring the end-to-end performance from the end-user perspective
–– Increasing scalability of the application by optimizing software and avoiding unnecessary hardware investments
While some of this discussion centers on LoadRunner specifically, it is important to note that these use-cases may be applied
using any load testing solution and methodology, not just LoadRunner.
LoadRunner transaction integration
The simplest and fastest way to get LoadRunner transactions in AppDynamics is ‘painting’ your LoadRunner requests. This
method involves adding a custom header that contains the LR transaction name in the request so that AppDynamics can
display the transactions exactly as they appear in LoadRunner. Adding a custom header in LoadRunner is a simple process using
LoadRunner’s built in capability to set headers, including custom headers. The end-result gives you the same visibility as you
have in LoadRunner, but with the following added benefits:
–– Deep code-level visibility, in the context of a LoadRunner Transaction, end-to-end
–– Application container-level data such as Heap size and usage along with standard and custom JMX metrics
–– Deep database visibility, in the context of the transaction, including details SQL breakdowns
–– Extended visibility into application infrastructure (CPU, Disk, Network, and Memory).
AppDynamics provides these benefits automatically without the need to configure multiple HP tools, such as HP SiteScope, and
then configuring LoadRunner to pull these metrics from HP SiteScope.
It is a simple two-step process to gain this visibility:
1. A minor modification to your VUGen scripts to set the header, using the web_add_header() function.
2. A minor configuration tweak in AppDynamics to detect this new header and name transactions accordingly.
In addition, the AppDynamics integrations team is working on a utility that will help make these changes in the VUGen script
automatically (as of October 2015).
Download the file to keep reading.