.ig
################################################################################
#
# (c) Copyright 1989-2002, Hewlett-Packard Company, all rights reserved.
#
################################################################################
..
.TH ttd.conf 4
.ds )H Hewlett-Packard Company
.ds ]W HP Measurement Interface
.SH NAME
ttd.conf - ARM registration daemon configuration file 
.SH DESCRIPTION
The ttd.conf file controls ARM registration via the ttd daemon.
It contains a list of transactions that may be registered.

This configuration file associates user-defined transaction names 
passed into arm_getid() with attributes such as Service Level Objective
(SLO) settings that are used for performance statistics bucketing
(such as TT_SLO_COUNT).
If the transaction entries are defined under 
a specific application, they are local to this application as passed
into arm_init(); otherwise,
they are defined for all applications.  The transaction tracking 
registration daemon, ttd, reads ttd.conf
to determine how to register ensuing user program ARM transaction 
requests.

Registration requests come from the 
.B arm_getid
function call.  
.B ttd
tries to match
.B arm_getid
requests using global and application-specific entries from the 
.B ttd.conf
file.  If an exact match fails, a pattern match against wild-carded
.B ttd.conf
entries is attempted.  Patterned entries are searched in descending 
order, based 
on the position of the pattern character.  Only trailing pattern characters 
are allowed.

The standard file location for
.B ttd.conf
is:
.nf
  /var/opt/perf/ttd.conf

.SH FILE FORMAT DETAILED DESCRIPTION

.SS Required keyword:
.TP 
.B [[application_name]]
.TP
.B tran=your_transaction_name [optional attributes...]
The transaction name following the 
.B tran
keyword cannot contain embedded spaces.  It can contain a trailing "*"
symbol to indicate that a wild card pattern match should be done when
matching registration requests against this entry.

.SS Optional keywords:
.TP
.B range=sec[,sec]+
Use 
.B range 
to specify the transaction performance distribution ranges.
.I sec
may be an integer or real number with a maximum of 6 digits to the right
of the decimal point.  The seconds may be specified to a precision of one
microsecond (0.000001 second) even though some performance tools may report
fewer digits.

A maximum of 10 ranges are supported.  This includes the upper most overflow
range that is added by transaction tracker to the user defined ranges;
therefore, you can specify 9 different ranges for each transaction.
.TP
.B slo=sec
Use 
.B slo
to specify the service level objective you want to use
to monitor the service level agreement (in seconds).

.SH EXAMPLES
.TP
.SS EXAMPLES
.TP
.B tran=mfg* range=0.001,1.0 
.IP "" 5
This line indicates that any arm_getid calls containing a name beginning with
.B mfg  
will be registered and have these performance distribution ranges.
.TP
.B tran=* range=0.5,1,2,3,5,10,30,120,300 slo=5.0
.IP "" 5
This is the default entry in the configuration file.  It indicates that all
arm_getid names will be registered and have these performance distribution
ranges and service level objective.
.TP
.B tran=Database_query slo=3
.IP "" 5
This line registers a user-defined transaction named 
.B Database_query 
for application named 
.B ap0
and specifies a service level objective.

.SH FILES
.nf
  /var/opt/perf/ttd.conf

.SH SEE ALSO
\fBttd(1)\fP, \fBarm(3)\fP, \fBmidaemon(1)\fP.