• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Ditmar P. · Mar 10, 2014 at 09:58 AM · continuous delivery

Loadrunner integration in Loadtesting - Unique transaction question

Hello,

We are currently working on a Loadrunner script for which the "Loadrunner script converter" does not work (Java VUser for simulating a Mobile Client with security etc...). We will build the headers ourselves, in the end Web request are being fired.

Looking at the funtion which normally gets created in a script which was converted I have a question :

void addDynaTraceHeader(char* header){
    char* headerValue;
    int headerValueLength;
    int vuserid, scid;
    char *groupid, *timestamp;
    char* vuserstring=(char*) malloc(sizeof(char) * 10);

    web_save_timestamp_param("TimeStamp", LAST);
    timestamp=lr_eval_string("{TimeStamp}");

    lr_whoami(&vuserid, &groupid, &scid);
    itoa(vuserid,vuserstring,10);

    headerValueLength = strlen(header) + 4 + strlen(vuserstring) + 4 + strlen(timestamp) + 1;
    headerValue = (char*) malloc(sizeof(char) * headerValueLength);
    strcpy(headerValue, header);
    strcat(headerValue,";VU=");
    strcat(headerValue,vuserstring);
    strcat(headerValue,";ID=");
    strcat(headerValue,timestamp);

    web_add_header("X-dynaTrace", headerValue);
    free(headerValue);
    free(vuserstring);
}

As far as I can see the header is made unique by the Timestamp in the above scenario.

Is it necessary to submit the ID= & VU= in the header for dynaTrace to see this request as unique? I can think of a high load scenario's where both will be the same.

By using a scenario with Groups the VU= nr would be the same, under high load the ID= (timestamp) could be the same effectively sending the same header for two different request, NA could also be the same.

Is this a problem, or is the dynaTrace agent capable of identifying these as unique requests anyway?

Thanks,

Patrick

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

2 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Ditmar P. · Mar 10, 2014 at 03:25 PM

Hello Andreas,

Thanks for the quick response. I will check the webinar.

Regards,

Patrick

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Mar 10, 2014 at 10:34 AM

Hi.

The VU and ID field in our HTTP Header are optional but we decided to fill them with information that might be useful later on to correlate these requests back to the Load Runner requests.

dynaTrace is capturing EVERY single request anyway as a PurePath and will also respond our unique PurePath ID back to Load Runner as a response HTTP Header. So - if you want to find the actual PurePath for a specific Load Runner request the best is to look at this HTTP Response Header. Take this value and then search for this PurePath by using the Tools -> Search PurePath menu.

Analyzing Load Test results however are typically not done on individual requests - unless you follow an e.g: slow or failed request from the load runner report to dynaTrace. In this case the best really is the approach from above. If you analyze load testing results in dynaTrace I do however suggest you start with our Load Testing Dashboard that gives you an overview of all your executed tests & steps and from there analyze the hotspots for those steps (=Timer Names) that showed performance or functional problem

There is also a webinar that you might be interested in: dynaLearn Webinar - Load Testing Made Easy with dynaTrace 4.2 - August 1, 2012

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

No one has followed this question yet.

Related Questions

Automation Dashlet and Browser metrics

Dynatrace Integration with Rational Performance Tester

Generating test performance reports in Jenkins from jenkins pipeline file

java.lang.IllegalArgumentException: No enum const class com.dynatrace.jenkins.dashboard.model.TestCaseStatus.INVALIDATED

dT 6.2 Testrun creation via REST not working

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A