Introduction

Silk Performer offers a plug-in framework for AppDynamics and other third-party diagnostics tools. The AppDynamics Plug-In is installed along with the Silk Performer setup. It is disabled by default.

AppDynamics focuses on monitoring performance at the Business Transaction level. Business transactions mirror end user activity and are defined as a category of user requests.

The current Silk Performer – AppDynamics integration supports automatic naming of such transactions based on Silk Performer timer names.

After successful configuration, an API call from Silk Performer such as the following:

BrowserNavigate("http://myserver.mydomain.com/login", "LoginPage");

Appears as the following business transaction in AppDynamics:

SilkPerformer.LoginPage

Configuring AppDynamics Plug-In Settings in Silk Performer

  1. From Silk Performer, select Settings > System Settings.
  2. Select the AppDynamics Plug-In group icon.
  3. On the General page, check the Enable plug-in check box.
  4. Configure name/value pairs on the Attributes page as required.
    The default Tag value is AppDynamicsTag.

    Note: A number of integration settings are dependent on the Tag attribute retaining the value AppDynamicsTag. If you change this default value, you will need to change additional settings, as explained below.

  5. Click OK to save your settings

Configuring Automatic Transaction Naming in AppDynamics

  1. In the left AppDynamics navigation pane, click Configure -> Instrumentation.
  2. Select Use Custom Configuration for this tier.
  3. Scroll down to the custom rules section of the page. 
  4. Click "+" to add a custom match rule.
  5. On the Transaction Match Criteria page, select Servlet from the drop-down list.
  6. Specify the name of the custom rule. 
    The name is the first part of the generated transaction name (Silk Performer in the image below).
  7. Specify the transaction match criteria:
    • For URI select Is Not Empty
    • Select Check for parameter existence and name the parameter AppDynamicsTag, as configured in Silk Performer.

  8. Select the Split Transactions using Request Data page and check the Split Transactions using Request Data check box.
  9. In the Apply a custom expression on HTTPServletRequest and use the result in Transaction names field, add the following string:
    ${getHeader(AppDynamicsTag).substring(Int/3)}
  10. Click Save.

So I have passed all this steps but I can't see any load. 

The Silk Perforemer server and AppDynamics server installed on the same machine. 

Should I installed additional Agent or what?