Loadrunner Unique Names

It is useful to be able to create human-readable unique names to be used for filenames, database keys, logging, etc.  One way to do this is to create a string with the following information:

• load generator name
• vuser id
• iteration number
• timestamp

This can be done easily as follows:

• get load generator name using lr_get_host_name()
• get vuser id using lr_whoami()
• get iteration number using a parameter of type iteration
• get current timestamp using lr_save_datetime()

The following script shows how to do this.

Script

Action()

{

int id

char *host; 

        // get load generator name

host = lr_get_host_name( ); 

//lr_output_message("Host: %s", host);

// get vuser id

lr_whoami(&id, NULL, NULL);

//lr_message( "Vuser id: %d",  id);

        // for iteration add a parameter named "Iteration" of type Iteration

//lr_output_message(lr_eval_string("Iteration: {Iteration}")); 

        // get timestamp, formatted as wanted

        lr_save_datetime("%m-%d-%Y-%I%M%S%p", DATE_NOW, "now"); 

//lr_output_message(lr_eval_string("Time: {now}"));

        // now generate the nice, readable unique id

lr_output_message(lr_eval_string("Host-%s-VuserId-%d-Iteration-{Iteration}-Time-{now}"),host, id);

return 0;

}

Output

Action.c(20): Host-generator02-VuserId-1-Iteration-1-Time-09-13-2012-035856PM [MsgId: MMSG-17999]

Action.c(20): Host-generator02-VuserId-2-Iteration-1-Time-09-13-2012-035856PM [MsgId: MMSG-17999]

Action.c(20): Host-generator02-VuserId-1-Iteration-2-Time-09-13-2012-035857PM [MsgId: MMSG-

Action.c(20): Host-generator02-VuserId-2-Iteration-2-Time-09-13-2012-035857PM [MsgId: MMSG-17999

Action.c(20): Host-generator02-VuserId-1-Iteration-3-Time-09-13-2012-035858PM [MsgId: MMSG-17999]

Loadrunner Current Timestamp

In Vugen, it is helpful to include a datetime with log messages, either informational or errors.  This can be done very easily using the lr_save_datetime function.  The timestamp can also be formatted in many different ways using the format codes commented out in the script below.   The following script shows how this can be done:

Script

Action()
{
// handle an event such as an error or important message including a timestamp
lr_save_datetime("%m/%d/%Y %I:%M:%S %p", DATE_NOW, "now"); 
lr_output_message(lr_eval_string("{now}: My important message here.")); 

//  Format codes for lr_save_datetime
// %a  day of week, using locale's abbreviated weekday names
// %A  day of week, using locale's full weekday names
// %b  month, using locale's abbreviated month names
// %B  month, using locale's full month names
// %c  date and time as %x %X
// %d  day of month (01-31)
// %H  hour (00-23)
// %I  hour (00-12)
// %j  number of day in year (001-366)
// %m  month number (01-12)
// %M  minute (00-59)
// %p  locale's equivalent of AM or PM, whichever is appropriate
// %S  seconds (00-59)
// %U  week number of year (01-52), Sunday is the first day of the week. Week number 01 is the first week with four or more January days in it.
// %w  day of week; Sunday is day 0
// %W  week number of year (01-52), Monday is the first day of the week. Week number 01 is the first week with four or more January days in it.
// %x  date, using locale's date format
// %X  time, using locale's time format
// %y  year within century (00-99)
// %Y  year, including century (for example, 1988)
// %Z  time zone abbreviation
// %%  to include the "%" character in your output string

return 0;
}

Console Output

Running Vuser...
Starting iteration 1.
Starting action Action.
Action.c(29): 09/13/2012 02:56:41 PM: My important message here.
Ending action Action.
Ending iteration 1.

How To Add a Timestamp to Each Line of Output on Linux

For performance monitoring on linux, you typically would like your shell script metrics and statistics that are logged periodically to include the timestamp with each line output.  That way, the information can later be correlated with other system events such as event log entries or system errors.  There are two basic scenarios.

1. Your shell script is echoing information to standard output periodically in some loop
2. You are just calling a program such as vmstat directly that outputs information periodically

Adding a timestamp in the two scenarios can be handled easily as follows:

Monitoring Loop

If your monitoring script includes a loop that is outputting stats periodically, a timestamp can be added to each line by capturing the output of the "date" command and then adding that information to the output line.

The output of the date command can be captured by using forward single quotes, as follows:

savedDate = `date`

Here is an example of a script making use of this technique:

#

# output stats every $1 seconds until stopped

#

if [ "$1" == "" ] ; then

  echo "syntax= .stats.sh <intervalSeconds>"

  exit

fi

time=$1

echo "Time , QueriesPerSechod" > mysql-stats.log

while :

do

    qps=`mysql -u mysql -e "show status" | awk '{if ($1 == "Queries") print $2}'`

    date=`date`

    echo "$date , $qps" >> mysql-stats.log

    sleep $time

done

Here is an example of the output:

Time , QueriesPerSecond

Wed Aug  8 16:11:58 PDT 2012 , 3029

Wed Aug  8 16:12:08 PDT 2012 , 18195 

Wed Aug  8 16:12:18 PDT 2012 , 18903

...

Direct Output

If you are just calling an app or script such as vmstat, iostat, etc., that outputs stats periodically for you, you can achieve the same effect by piping the command through an app that prepends a timestamp to each line.  For example, to prepend timestamps to the output from vmstat, free, and iostat, you would do the following, depending on a script "timestamp.sh" with the timestamp prepend behavior:

# free

free -g -s 10 | ./timestamp.sh > free.log &

# vmstat

vmstat 10 | ./timestamp.sh > vmstat.log &

# iostat

iostat 10 | ./timestamp.sh > iostat.log &

This would give output such as the following:

07/23/12 10:41:44,procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----

07/23/12 10:41:44, r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st

07/23/12 10:41:44, 6  0   2736 3381052 505844 159601296    0    0    62   119    1    1  6  1 93  0  0

07/23/12 10:41:54, 2  0   2736 3358836 505900 159601728    0    0   102    25  640  414  1  0 99  0  0

07/23/12 10:42:04, 7  0   2736 3329736 505948 159601936    0    0     9    32  927 1263  1  0 98  0  0

The timestamp.sh script is as follows:

#!/usr/bin/perl

#while (<>) { print localtime() . ": $_"; }

while (<>) 

{

($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);

$secpad = sprintf( "%02d", $sec );

$minpad = sprintf( "%02d", $min );

$hourpad = sprintf( "%02d", $hour );

$monpad = sprintf( "%02d", $mon );

$mdaypad = sprintf( "%02d", $mday );

$yearpad = sprintf( "%02d", ($year + 1900) % 100 );

$time = "$monpad\/$mdaypad\/$yearpad $hourpad:$minpad:$secpad";

print $time . ",$_" ;

#17/04/112 16:40:14

}