ttd.conf(4)ttd.conf(4)NAMEttd.conf - ARM registration daemon configuration file
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 spe‐
cific 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 deter‐
mine how to register ensuing user program ARM transaction requests.
Registration requests come from the arm_getid function call. ttd tries
to match arm_getid requests using global and application-specific
entries from the ttd.conf file. If an exact match fails, a pattern
match against wild-carded 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 ttd.conf is:
/var/opt/perf/ttd.conf
FILE FORMAT DETAILED DESCRIPTION
Required keyword:
[[application_name]]
tran=your_transaction_name [optional attributes...]
The transaction name following the tran keyword cannot contain
embedded spaces. It can contain a trailing "*" symbol to indi‐
cate that a wild card pattern match should be done when matching
registration requests against this entry.
Optional keywords:
range=sec[,sec]+
Use range to specify the transaction performance distribution
ranges. 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.
slo=sec
Use slo to specify the service level objective you want to use
to monitor the service level agreement (in seconds).
EXAMPLES
EXAMPLES
tran=mfg* range=0.001,1.0
This line indicates that any arm_getid calls containing a name
beginning with mfg will be registered and have these performance
distribution ranges.
tran=* range=0.5,1,2,3,5,10,30,120,300 slo=5.0
This is the default entry in the configuration file. It indicates
that all arm_getid names will be registered and have these perfor‐
mance distribution ranges and service level objective.
tran=Database_query slo=3
This line registers a user-defined transaction named Data‐
base_query for application named ap0 and specifies a service level
objective.
FILES
/var/opt/perf/ttd.conf
SEE ALSOttd(1), arm(3), midaemon(1).
ttd.conf(4)
