Persisting tagged transactions
This topic describes the configuration parameters to persist transactions that have tags in the headers.
If you use an external monitoring application that can tag transaction headers, App Visibility can provide a detailed view of specially tagged transactions. Transactions with matching tags are persisted, regardless of sampling or threshold configuration.
Warning
To prevent adverse system performance, use tagging on a very limited number of transactions.
The following table describes the parameters used to list the tags and persist transactions.
Parameters that control the persistence of tagged transactions
Parameter | Default value | Description |
---|---|---|
| true | When true, the agent persists transactions with headers that match the value or values of the persisting.tag.header.names parameter |
persisting.tag.header.names |
| Includes predefined HTTP header tags. Separate more than one tag with a comma. The default value is set to capture synthetic transactions from BMC TM ART. |
| Enter a value for one of the Note: If more than one value is entered, only the first tag with a value is used, per request. The value of the integration tag must conform to the following characteristics:
|
Access the tagged request with a hyperlink built according to the following syntax:
https://<consoleHost>/console-adops/view/singlerequest/
singlerequestdetails.jsf?tag=<yourTagValue>
- <consoleHost> is the host name or IP address of the TrueSight console.
- <yourTagValue> is the value of the header, request name, or cookie integration tag.
Comments
Log in or register to comment.