See the dynaTrace blog for a hands-on introduction incl. a step-by-step guide and screenshots.
SilkPerformer Plugin 3.2.1+
dynaTrace 3.2.1 and later
SilkPerformer 2007, 2008, 2008 R2, 2010, 2010 SP1, 2010 R2, 2011
dynaTrace Experimental Software License
SilkPerformer Plugin for dynaTrace 6.3
SilkPerformer Plugin for dynaTrace 5.6 SilkPerformer Plugin for dynaTrace 5.5 SilkPerformer Plugin for dynaTrace 5 SilkPerformer Plugin for dynaTrace 4.2 SilkPerformer Plugin for dynaTrace 4.1 SilkPerformer Plugin for dynaTrace 4 SilkPerformer Plugin for dynaTrace 3.5 SilkPerformer Diagnostics Plugin v3.2.1
SilkPerformer 2010 SP1 ships with SilkPerformer Diagnostics Plugin v3.2.1 embedded.
Copy the plugin to the <SilkPerformer_home>\Working\Plugins directory and extract it. Start SilkPerformer, choose "Settings" -> "System" and scroll down in the left side bar until the plugin is visible.
Figure: SilkPerformer Plugin installed in SilkPerfomer
Some SilkPerformer versions come with a dynaTrace Diagnostics Plugin installed. Please deactivate this plugin to use the SilkPerformer Plugin .
The SilkPerformer Plugin offers the ability to record a session when a load test (even a try script) is started. This can be done by setting the option "Automatic Session Recording" in the Plugins "Attributes" tab to true.
"Automatic Session Recording"
The "Wait Timeout" Attribute determines the time the SilkPerformer is waiting for the dynaTrace Client to be started. If the dynaTrace Client cannot be reached within this interval the load test will start without dynaTrace session recording.
The "System Profile" Attribute determines the dynaTrace System Profile on which session recording should be started. If omitted, session recording will be started on the first System Profile on the dynaTrace Server with an Agent connected.
The "SilkPerformer Diagnostics Client Port" Attribute determines the dynaTrace client REST interface port.
"SilkPerformer Diagnostics Client Port"
If the dynaTrace Client is connected to multiple dynaTrace servers the first connected server will be used.
If you change the configured server in dynaTrace Client SilkPerformer has to be restarted.
SilkPerformer Plugin 3.2.0 and earlier
This is the SilkPerformer Plugin for dynaTrace 3.2 and earlier.
SilkPerformer 7.2, 7.3, 2006, 2006 R2, 2007, 2008, 2008 R2
dynaTrace 3.0 - 3.2
SilkPerformer 2007, 2008, 2008 R2, 2010, 2010 SP1
SilkPerformer Plugin v3.2 SilkPerformer Plugin v3.1 SilkPerformer Plugin v3.0.1
Copy the Plugin to the <SilkPerformer_home>\Working\Plugins directory and extract it. Start SilkPerformer, choose "Settings" -> "System" and scroll down in the left side bar until the dynaTrace Plugin is visible.
Figure: dynaTrace Plugin installed in SilkPerfomer
Most SilkPerformer versions come with a dynaTrace Diagnostics Plugin installed. Please deactivate this Plugin to use the dynaTrace Plugin with dynaTrace 3.0 / 3.1.
The dynaTrace Plugin offers the ability to record a session when a load test (even a try script) is started. This can be done by setting the option "Automatic Session Recording" in the Plugins "Attribute" tab to true.
The "Application Session" Attribute determines the dynaTrace System Profile on which session recording should be started. If omitted, session recording will be started on the first System Profile on the dynaTrace Server with an Agent connected.
If the dynaTrace Client is connected to multiple dynaTrace Servers there may be problems with matching the correct System Profile. If the System Profile is available on multiple dynaTrace Servers, it is possible that session recording is started on the wrong Server. If the "profile name" attribute is omitted, session recording may be started on any of the connected dynaTrace Server on the first System Profile with an Agent connected.
SilkPerformer JMX Browser Patch
This is the SilkPerformer JMX Browser Patch for dynaTrace 3.0.x and 3.1.
SilkPerformer 2006, 2006 R2, 2007, 2008, 2008 R2, 2009
dynaTrace 3.1 dynaTrace 3.0.x
SilkPerformer 2007, 2008, 2008 R2, 2009
All currently available SilkPerformer versions are missing the JMX integration data for dynaTrace 3.0. To be able to use dynaTrace 3.0 JMX data please follow the steps below.
Copy the zip file to <SilkPerformer_home>\Working and extract it. A dynaTrace 3.0.xml will be extracted to <SilkPerformer_home>\Working\Include\jmx-config. Open the realtime.ini located in <SilkPerformer_home>\Working\Include. Adapt the file as indicated by the excerpt below.
Add the following line to "Application In-Depth": C= JMX:dynaTrace 3.0, Application In-Depth\dynaTrace\dynaTrace 3.0 (JMX MBeanServer),dynaTrace 3.0 (JMX MBeanServer)
The installation is finished and the JMX data of dynaTrace 3.0 is now available in SilkPerformer.
Open "Silk Performance Explorer" and choose "Monitor" -> "Add Data Source". In the "Data Source Wizard" choose "Select from predefined Data Source" and click "Next". Open "Application in-Depth" -> "dynaTrace" -> "dynaTrace 3.0" and click "Next".
"Silk Performance Explorer"
"Add Data Source"
"Data Source Wizard"
"Select from predefined Data Source"
Fill in the correct data in the connection parameters dialog:
Choose the JMX values you want to monitor:
It would be nice were there a "ReadMe" file embedded within the plug in - as things are a bit confusing because when one installs Silk Performer 2011 the embedded plug in files are:
C:\Program Files\silk\SilkPerformer 2011\Plugins\old_dynaTrace\StyleSheet.css
C:\Program Files\silk\SilkPerformer 2011\Plugins\old_dynaTrace\api.gif
C:\Program Files\silk\SilkPerformer 2011\Plugins\old_dynaTrace\banner_left.jpg
C:\Program Files\silk\SilkPerformer 2011\Plugins\old_dynaTrace\dtreporticon.gif
C:\Program Files\silk\SilkPerformer 2011\Plugins\old_dynaTrace\logo.gif
C:\Program Files\silk\SilkPerformer 2011\Plugins\old_dynaTrace\path.gif
C:\Program Files\silk\SilkPerformer 2011\Plugins\old_dynaTrace\perfPIdynaTrace.dll
However, when one downloads the new plug-in for Dynatrace version 4.1 it contains the following files -
C:\Program Files\silk\SilkPerformer 2011\Plugins\new_DynaTrace\dynatrace-viewer-126.96.36.19998.msi
C:\Program Files\silk\SilkPerformer 2011\Plugins\new_DynaTrace\dynatrace-188.8.131.5298-x64.msi
C:\Program Files\silk\SilkPerformer 2011\Plugins\new_DynaTrace\dynaTrace_license_201112131035.key
C:\Program Files\silk\SilkPerformer 2011\Plugins\new_DynaTrace\dynatrace-agent-184.108.40.20698.msi
which end up looking like install files for the DynaTrace product, not for a plug in to Silk Performer?
When I download the latest plugin version for dynaTrace 4.1 that is attached to this community page then I get a zip file that contains the correct files (stylesheet.css, api.gif, ...). Here is the download for the dynaTrace 4.1 SilkPerformer Plugin
Where did you download the 4 files that you have listed? One of the files is actually a license key which we would not put into a plugin download.
Can you please clarify where you have downloaded these files?
Does this plugin add the Tags for Tagged Web Requests? I have a client whose requests seem to have a non-functioning http tag being injected but they can't find it in the scripts. Their plugin is out of date at this point, I believe, is it due to some change in the name of the tagging header since 3.5?
Hi Richard. I am not sure I understand what you mean with "non functioning http tag?". Do you mean that the tag that gets inserted doesnt end up as tagged web request in dynaTrace?
There was a change in the HTTP Tag - but - it should still be backward compatible. The SP Plugin simply adds the HTTP Header to all Web Requests. The header value name is "dynaTrace". The value will include the current "Timer Name" and Virtual User ID. That should work. If it doesnt work as expected I suggest to look at the "TrueLog" from Silk to see whether the header is really set -> this can be seen in the TrueLog for all Web Requests. If you see the header there then make sure that there is no proxy/firewall between Silk and the AppServer that removes that header
Hello, my customer uses SilkPerformer to test their whole environment sending request throught their load balance, does we need to have a dT Webserver agent to get those at the "Tagged Web Requests" dashlet??
Currently we have dT agents only at the App tier (Weblogic) and we didn't see any request at the "Tagged We Requests" dashlet.
We did see the plugin working before with a .Net Application, but we had issues with this Apache+Java environment.
It should work in the same way for JAva as .NET. You also dont need the Web Server Agent for this. What you need to make sure is that the additional HTTP Header that SilkPerformer puts on each request is not filtered out somewhere between SilkPerformer and the Servlet Filter that starts your PurePath. The HTTP Header is called "dynaTrace" or "X-dynaTrace". So - make sure that these HTTP HEaders are not blocked or filtered out somewhere
Does the dT client have to be installed on the same machine silk performer is running?
Currently I am looking at running silk performer on a box in amazon cloud and dT server is hosted internally. Will manually doing the tagging in silk performer have to be used in this option?
SilkPerformer can run anywhere. Tagging will work regardless on whether you have it running on the same box or not.
The only thing that requires SilkPerformer Workbench to run on the same machine as the dynaTrace client is if you want to enable Automatic Session Recording or if you want to lookup a PurePath from your TrueLog Explorer. But - you dont necessarily need Automatic Session Recording if you have Continuous Session Recording turned on in dynaTrace (ON BY DEFAULT). And as for the lookup. You can install TrueLog Explorer on your local machine and from there then jump to the PurePath. But - I would almost recommend looking at the Load Testing Results through the Load Testing DAshboard in dynaTrace. Thats a great way to start. More information about Load Testing can be found here: Dynatrace for Testers
Has anyone tested the latest plugin with SilkPerformer version 15? http://community.microfocus.com/borland/test/silk_performer_-_application_performance_testing/b/weblog/archive/2014/02/21/announcing-silk-performer-15-0.aspx
Is there a version of this plugin available for 6.0?
all the best
Hi JMI - the plugin interface hasnt changed. thats why you should be able to use the latest version of the plugin (5.6) and also use it against 6.0
What about dynaTrace version 6.1? Still use dT version 5.6 plugin for Silk Performer (which is now at version 15.5)?
Yeah - nothing really has changed there
We are using Silkperformer's Browser Driven client for our load tests This starts up a customized IE engine in silk performer so that this engine can load the entire web page and even run the java script programs on the page Session handling and dynamically changing pages are handled automatically but when we interface the test using the dynatrace 56 plugin we do not see the test name or script name in dynatrace We are using silk performer 155
I am thinking that the missing dynatrace info is because we can no longer set the HTTP headers in the browser driven script API All the API calls interface with the IE engine so we have script calls that are browser clicks
Has anyone ever gotten silk performer browser driven scripts to send the required dynatrace HTTP tags to dynatrace?
I use dynatrace with Browser driven scripts in silk performer. I put the name I want for my purepath in the "timer name" of each web request. Then the purepaths have that name. I don't have to have a webheaderadd in the scripts.
This purepath would be the value of: suser+"_01_Login");
this one the value of: suser+"_03_PymntConfirmBtn
Not sure if this is required, but I have had better luck also ensuring the name of the system profile is called out in the attributes tab of the SilkPerformer Diagnostics Plugin under system settings.
Hi Thomas. You are correct. The problem is that Silk doesnt add any dynatrace HTTP headers for these types of test scripts. The only "workaround" that I see is that you use tools like Fiddler that can add these headers for you while executing your scripts. There is an article from one of our users that explains his work on QTP where he tried to solve a simliar problem: How to injecting dynaTrace HTTP Header using an HTTP Proxy
Hi Andreas, The article about using Fiddler to inject HTML tags mentioned a CustomScript,js. Can you send me that script?
Hi Thomas. I looked at my Fiddler installation but couldnt find my custom script anymore. As far as I remember it was really simply. I just added the X-Dynatrace header to it. In Fiddler you can edit the custom scripts via Rules -> Custom Rules. There you will find the custom script file where you can add your own code to modify the HTTP Requests. I extended the OnBeforeRequest method and added the X-dynatrace header. So - it should be pretty straight forward
where can I find plugin for 6.1 ?
The latest verison of the plugin will also work for 6.1. thats why there is no special plugin version for 6.1
When I run the test from SilkPerformer 16, this is the error when start :
4:10:29 PM Info 0 Could not get client version. REST request failed4:10:29 PM Info 0 SilkPerformer Diagnostics Client not present4:10:29 PM Error 0 Cannot find SilkPerformer Diagnostics Installation
What is the "SilkPerformer Diagnostics Client Rest Interface Port" ? 8030 ?
Also, I can't find the plugin in Dynatrace 6.1 "installed plugin" .. Do I need to add a file ?
Where can I get it ?
Port 8030 is the one that is listed in our default installation of Silk Performer 16 & dynaTrace v. 6.1; - which shows as the "Silk Performer Diagnostics Client Port"
In Silk Performer v.16 when we want to enable the dynaTrace 6.1 plugin (which came with Silk Performer 16) we merely go to SETTINGS -> SYSTEM (scroll all the way to the bottom icon) -> Silk Performer Diagnostics Plugin > check the box "Enable plug-in" in the right pane.
And as a sanity check, the plug-in files that came with Silk Performer are located here:
C:\Program Files (x86)\Silk\Silk Performer 16.0\Plugins\dynaTrace
If perchance you had to go get them from dynaTrace, then the 5.6 version would work, and copy them into the above directory.
does the Silk Performer plugin for Dynatrace AppMon 6.3 work also for Appmon 6.5 ?
Sorry for the late reply. The Plugin should just work as for 6.3. The integration points havent changed, e.g: Tagging Web Requests, ...