
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
My question is specifically around HOW the silk timer is tagged to the request in Dynatrace.
With the Dynatrace plugin enabled, any request that has a TIMER, as shown below, will show up with a purepath name matching the timer name.
With the plug-in disabled, the generic URL is used for the purepath name.
WebPageCustomRequest ("GET", "https://URL/PRAjax.action", WDCJ009, "PatRev3_1Fac5Pop_PatLvlSrch.action", WDCJ010);
WebPageCustomRequest( in sMethod : string,
in sUrl : string,
in formBody : form optional,
in sTimer : string optional,
in formUrl : form optional ): boolean;
Is it something inserted in the header? I'll be asking Dynatrace support this same question and will report back what I find.
Thanks!
Don
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Don,
Silk Performer's dynaTrace integration works by adding dynaTrace information in the headers to tag the requests.
For example:
X-dynaTrace:+VU=1;PC=.53;ID=258554980;NA=Click,+IMG,+id=ext-gen6+(#1)
When the dynaTrace plugin is enabled you should be able to view this header information in the "Out Header" tab of the TrueLog.
Best Regards,
Neil

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Don,
Silk Performer's dynaTrace integration works by adding dynaTrace information in the headers to tag the requests.
For example:
X-dynaTrace:+VU=1;PC=.53;ID=258554980;NA=Click,+IMG,+id=ext-gen6+(#1)
When the dynaTrace plugin is enabled you should be able to view this header information in the "Out Header" tab of the TrueLog.
Best Regards,
Neil