Test Name with SilkPerformer Plugin
Hi,
When we activate the SilkPerformer Diagnostics Plugin, it seems we only pass the Timer Name by default. Is there a way that the scripts/tests have to be set up to get the test name into the tag also? This would be great for using the Test Automation dashlet with load tests.
Thanks,
Rick B
Hi Rick
The PM of Silk told me that there are more options available - probably in a newer version of Silk as the one you are using. Here is the list of options with some sample values next to it:
WebSetHttpTag("x-dynaTrace",
WEB_TAG_FLAG_RequestId | // ID=1
WEB_TAG_FLAG_UserId | // VU=1
WEB_TAG_FLAG_PageContext | // PC=.1
WEB_TAG_FLAG_Timer | // NA=Demo+Borland+Com
WEB_TAG_FLAG_Agent | // AN=localhost
WEB_TAG_FLAG_ProjectName | // PN=DynaTraceTags
WEB_TAG_FLAG_UserGroup | // UG=WebUser
WEB_TAG_FLAG_Profile | // PF=Profile1
WEB_TAG_FLAG_Workload | // WL=Workload1
WEB_TAG_FLAG_Transaction | // TN=TWeb
WEB_TAG_FLAG_BrowserSession | // SI=1
WEB_TAG_FLAG_WorkloadType | // WT=3
WEB_TAG_FLAG_LineNumber | // LN=49
WEB_TAG_FLAG_Time ); // TI=1403008918
Andi
That's awesome! I will inform the customer. It would be great if one of the following options was available for Test Name:
- Allow for modification of the flag (to use TE instead of PN for ProjectName is my immediate use case)
- Include a separate flag TestName or ProjectNameTE which does the same
- Allow dynaTrace to recognize ProjectName
I can submit an RFE for the third one, but wondering what you/<Silk-PM> might think is most feasible.
Thanks
Rick
FYI - I just heard back from the SilkPerformer Product Manager. He is forwarding this to his engineering lead so that this gets addressed in future Silk versions
Great! Thanks a lot Andi, please feel free to share my info if they need user feedback.
Rick
Unfortunately there has not been a whole lot of improvements in that integration as the official partnership between Compuware and MicroFocus ended a while back. Thats why recent extensions to the TAG are not available in SilkPerformer. I will reach out to my former colleagues over there and see if they can still make it happen
On your side - maybe you can talk with the customers so that they also reach out to MicroFocus asking them about ongoing investments in the integration
Andi
Thanks Andi,
It does not seem this is exposed/configurable in Silk or at the OS level but I was able to take your recommendation and pair all the available tags SilkPerformer provides with the ones that dynaTrace accepts and we put this in the tinit for the scripts:
dcltrans
transaction TInit
begin
WebSetHttpTag("x-dynaTrace",
WEB_TAG_FLAG_RequestId |
WEB_TAG_FLAG_UserId |
WEB_TAG_FLAG_PageContext |
WEB_TAG_FLAG_Timer |
WEB_TAG_FLAG_Agent);
end TInit;
If it turns out this is not configurable as it seems, can we compile it with the new header values and send a new version over to MF for future releases?
P.S. we still are missing test name here (would be "Project Name" which uses PN instead of TE), I would add the request that if the plugin were to be re-distributed we'd find some way to take this variable and re-assign it to TE, or else allow dynaTrace to see PN.
Thanks,
Rick B
Hi Rick
The SilkPerformer integration was built before dynaTrace offered the additional tags Script Name, Geo Location, ... (that all came around the time when we tightened our integration with Gomez).
I dont have SP installed on my machine but I think I remember that the X-dynatrace HTTP Header is set through a BDL script that comes with the plugin. You could try to modfiy this BDL script that creates that header and add the additoinal information you need.
If I am wrong with that BDL script you could just write your own little helper method that generates the X-dynaTrace HTTP Header including all the information you need. SilkPerformer offers a method called WebSetHttpTag where you can set your custom tag
Hope this helps
