Planning Project Attributes

For this tutorial you will plan three measures. Pick measure names that indicate the hierarchy and purpose of the measures. In this example, a measure counts the number of processes on a SunOs system and includes two measures that measure HTTP requests (Performed using WebUrl):

The intended hierarchy will then look like the following:

  SunOs
    Processes
      CountNrOfProcesses
    Http Server
      URI1
      URI2

A BDL script with two user groups and two transactions is written. See the table below to see how measures are assigned to transactions and how transactions relate to user groups.

User Group Transaction Measure
VMonitor TSnap CountNrOfProcesses
VWebMon TWebSnap URI1
VWebMon TWebSnap URI2

With projects that include numerous transactions and/or user groups, measures must be specified with the corresponding user group and assigned measure. This differs from the basic use case outlined previously, which involved only one transaction and one user group.

Open the project attributes editor at Projects > Project Attribute and enter the following data:

Name Type Value
#BDLMonitor1.Name string SunOs\Processes\CountNrOfProcesses
#BDLMonitor1.Type string AvgCounter
#BDLMonitor1.Enabled boolean True
#BDLMonitor1.Script string remote.bdf
#BDLMonitor1.Usergroup string VMonitor
#BDLMonitor1.Transaction string TSnap
#BDLMonitor2.Name string SunOs\Http Server\URI1
#BDLMonitor2.Type string AvgCounter
#BDLMonitor2.Enabled boolean true
#BDLMonitor2.Script string remote.bdf
#BDLMonitor2.Usergroup string VWebMon
#BDLMonitor2.Transaction string TWebSnap
#BDLMonitor3.Name string SunOs\Http Server\URI2
#BDLMonitor3.Type string AvgCounter

#BDLMonitor3.Enabled

boolean True

#BDLMonitor3.Script

string remote.bdf

#BDLMonitor3.Usergroup

string VWebMon

#BDLMonitor3.Transaction

string TWebSnap
host sunserver sunserver
command string ps -ef | egrep -c ".*"

user

string root
password password ***********

URI1

string

/

URI2 string /manual/ibm/index.html